Marcin PetrówIt started very slowly. Lukasz (https://www.linkedin.com/in/lukaszciechanowicz/) shouted that he created a blog, and we can find something there, something for us. Deep breath, and in the next few minutes I was there. Easy thing (you can read about it here: https://notes.ciechanowi.cz/notes/a-blog-i-dont-have-to-babysit/) - just take what is there and bring your own thing live quickly.
The start was good
The first 15 minutes were fast. Fork created. Cloned to local. I’m in.
Second look: what do we have, and why do we have what we have? Everything looks as it should. Astro “engine” was in place and was enough to run daily posts without any issues. A mature approach from the start should always keep things from getting overcomplicated.
As I always say: “Don’t complicate your things; life is gonna do that for you.”
What I liked about what he did was sharing this with us. Just like that. He’s good at it. Another thing is that it’s very easy to get into. So, in all those things, in my mind, I did sit comfortably in my chair and start thinking about how to move to my own blog with his help.
My brain did the job
But the bad one. Because right after my legs spread out under the desk, I started looking for things that maybe would be useful. Drafts?! Can I?
The answer was yes. The approach was very simple: under each post, I can add a flag that says - Yes! That’s Draft.
Ok, but can I switch themes?! It’s easy to understand that this is the most valuable thing to have at the beginning. Not content, not already created automation, themes! After a quick search, I found an answer. Possible, easy to make; I need to have it. For sure, you know what happened next. Of course, it did take time. But now I have it.
Maybe this is a time for a post
No! For sure, I missed something. My strongly engineered brain, after so many years, did that to me. Let’s go dig again.
We got it: I don’t see any information about BoldMerge. All my projects these days have it, and I won’t start without it. Branding is important; marking your territory is what counts most now. So let’s go and add this one. After finding graphics and samples from other apps, I was ready to introduce it here, too. Proud that this has sat with me for so long, and it’s so well prepared to use.
But I stopped here.
Fun was killed
Overengineering as a fun killer.
That was the point where I was looking for excuses not to write my first post. It’s not about not having content. It’s about postponing the result, searching for a better solution to what we already have. Theory is simple. We should work incrementally and, as much as we can, gather feedback, and then wait until we have this ask. Taking this too far could lead to a point where turning back will be painful.
Since when is fun painful?
What Lukasz did was remind me why being an engineer was fun for so many years. Why those projects called POC, MVP, FromScratch were so satisfying. Maybe some of them were never finished. But except for the hard work that had to go into them, I got a lot of fun doing them. That was the fuel for solving cases. To dig deeper.
Why is it important?
We teach people these days how they should drive their career. Where to find passion and energy to do stuff. Why the combination of hard work, resting, and keeping the goal in front of them is so important.
Sometimes forgetting why it’s also important for us.
