I can definitely relate to the part that talks about analysis paralysis. When starting a new project, like everybody else, I'm usually faced with several differ

I can definitely relate to the part that talks about analysis paralysis. When starting a new project, like everybody else, I'm usually faced with several different options on how I'm going to design it, which libraries I'm going to use, what the overall architecture is going to look like, what features I'll implement and so on. And very often, I get stuck deciding between two options, weighing which one is better, which one might prove to be a bad decision in the future and which one might make my code more flexible/inflexible to change and refactoring. But then I slap myself (figuratively, of course) and remember to "just do it". To just release any kind of working code, never mind if it's a suboptimal design, never mind if there are a few bugs or if it's slower than it could be. The important thing is to release anything. The code can be improved upon after that.