by ioncube on 2/25/25, 8:19 PM with 1 comments
Here is a recent example: I had an idea for an app so I started researching which language/framework I should use, I ended with two or three options. So I picked up one and went over the docs and decided to start building my app along the way.
I did a small progress and I thought "It would be cool if I could implement some kind of lightweight ORM for my app" and remembered that one of the languages had a feature which lets you write SQL-like expressions in code, and then I started wondering if I should implement very basic version of it by myself.
At this moment, I am still interested developing my app but the journey has gotten longer to achieve it and if I look back at my history, there is a 95% chance I am going to abandon the original idea too.
It seems I go on an endless side quests. I do learn stuff along the way but it's happening in pieces, a little here and little there.
In the end, I have garden of unfinished side projects, books and courses. I start every idea with motivation but then a new interesting idea pops up in my head and I go after it.
Here is another one: when writing documentation I tend to go back and forth frequently to change wording until I am satisfied, same with variable names - "too long" / "it is confusing" / "can be more descriptive".
I am curious if more people are experiencing this and how they handle it.
by PaulHoule on 2/25/25, 8:28 PM