How to get your pet projects done
Frankly, I’m writing this post because I’m struggling to finish my current pet project—despite fully understanding what needs to be done. And you’re probably thinking, “What the hell is he saying? If you know what to do, then just do it!” And you’re right. The reason I haven’t finished my project yet? Overcomplicating things. I saw a nice feature on a website that allowed users to switch themes and languages seamlessly. I got jealous. I thought, “I can do the same thing—maybe even better!” So, I started implementing a theme switcher. I spent two days making it just right—following a solid architecture, ensuring it was convenient to use. Eventually, I was satisfied with the result. But then it hit me… I had just procrastinated for two days. This is the worst kind of procrastination—the one that looks like real work. But it’s not. You know why? Because even if you achieve a great result, it means absolutely nothing if it doesn’t bring you closer to your final goal. Let me put it more clearly: at the start of any project, I define an MVP (Minimum Viable Product)—a simple version that covers the basics and can be deployed as the first iteration (which, let’s be honest, you probably won’t improve later). I’m sure you’ve been in the same situation. How many times have you found yourself working on something outside your MVP? Design, routing, documentation (of course, you won’t remember what these two functions do without solid documentation, right?). At first glance, it all seems important. It feels like progress. But is it really? I want to share what helps me get back on track when I stray from my goals:
Frankly, I’m writing this post because I’m struggling to finish my current pet project—despite fully understanding what needs to be done. And you’re probably thinking, “What the hell is he saying? If you know what to do, then just do it!” And you’re right.
The reason I haven’t finished my project yet? Overcomplicating things.
I saw a nice feature on a website that allowed users to switch themes and languages seamlessly. I got jealous. I thought, “I can do the same thing—maybe even better!” So, I started implementing a theme switcher. I spent two days making it just right—following a solid architecture, ensuring it was convenient to use. Eventually, I was satisfied with the result. But then it hit me…
I had just procrastinated for two days.
This is the worst kind of procrastination—the one that looks like real work. But it’s not. You know why? Because even if you achieve a great result, it means absolutely nothing if it doesn’t bring you closer to your final goal.
Let me put it more clearly: at the start of any project, I define an MVP (Minimum Viable Product)—a simple version that covers the basics and can be deployed as the first iteration (which, let’s be honest, you probably won’t improve later).
I’m sure you’ve been in the same situation. How many times have you found yourself working on something outside your MVP? Design, routing, documentation (of course, you won’t remember what these two functions do without solid documentation, right?). At first glance, it all seems important. It feels like progress. But is it really?
I want to share what helps me get back on track when I stray from my goals:
