A few days ago I came across this article. The author shows how to access a Drupal system in the backend with a Vue.js app. For authentication he uses an API key - and I find that dangerous. Here's why.
This is a call to mediocrity. Do things without intending to hit the big time. Do! Start! Don't think about the output, but make the way to your goal. Yes: all too often you've set out to do it, and yet you've failed again and again to meet your standards. Every text, every website, every important email: you've twisted words, deleted sentences, and rewritten. Often enough you crumpled things up afterwards and threw them away. But how much didn't get done in the first place?
Have you ever heard of the Fediverse? Not me. At least until a few days ago, when @hagengraf told me about his Instagram alternative Pixelfed on Twitter and in a blog post.
Leverage effects allow us to have an impact far beyond our actual size. They are a multiplier of our results. The effort I invest is multiplied by the leverage effect and added to the result.
It's been a while since I published the last blog post. But the time at the end of a year is a special time: it gives you a chance to shut down and take a fresh look at things with some distance. Unfortunately, the importance of distance from everyday life only becomes apparent when you've already gained that distance.
For a few days I have been carrying a quote around with me: "The effort is enough". I got it from the book "Ego is the enemy" by Ryan Holiday. It's a fantastic sentence that exudes incredible serenity.
This quote means that success should be measured by the effort we put into our goals, rather than merely looking at the outcome. And this basically aligns with my view of goals: focus on the things you have control over, rather than things that are out of your control.
The time I take to work, I want to make as effective as possible. I therefore avoid surfing the web or writing messages on my smartphone at the same time. Instead, I try to jump right into the work process and generate a flow that carries me quite a bit through my tasks. But I have many different projects going on at the same time, and I've often found myself unable to choose one to keep working on, despite having so many projects. It was a bit like the forest you can't see for the trees.
I'd like to start a little series under "Sunday Thoughts" where I briefly share ideas that have been on my mind over the week or projects I'm currently working on. Starting today is "Sunday Thoughts 1"
On my way to develop a 3D printable camera drone I designed and printed different housings and frames. But I always came to a point where I had to make changes: sometimes I had to reposition the GPS unit, change the position of the camera, relocate cables, etc. I had to make a lot of changes. All this led me to discard the design again and again and develop a new one. This slowed me down a lot in the development, so I decided to create a flexible and quickly customizable development framework.
I was confronted with a Supabase problem that (almost) drove me crazy: I have a simple table "projects" that only stores a project uuid and a project name. While developing on my Web-App I disabled role level security (RLS) for this table. I usually proceed disabling row level policies in the first phase of developing as it helps me to focus on the frontend and the general project scheme.
