Procrastination is connected to perfectionism

I would comment on this issue, but I am still thinking about what the best comment would be....

As a public open source (yep, open source can be private) programmer (currently x86_64 assembly), and I am very aware of this pitfall.

It is very important to move forward in code, because you cannot predict how will actually end up a complex program: you need to have all the (sane) features in to actually know. Since code is all about trade-offs, there is "no perfect".

You have to be carefull at avoiding falling into a mental spinning loop about this.

Once you have a reasonable minimum of usable features in, publish it. It help breaking such mental loop.

For instance, currently writing a printf implementation, and printf specs are already brain damaged by themselves, so I am not looking for perfection, far from it. I did set myself a minimal set of features (full format decoding, hexadecimal and byte strings) before publishing it. Until it does not require the complexity of a compiler, does a good enough job, I'll be happy.

Sometimes it is not about perfectionism, but a question of resourses required to achieve something reasonably working: you have a montain to deal with just to get something minimaly working, and you are given a spoon... when you are lucky.

“The fall is worth the climb” -Mike Tyson.

I think this is kind of like, if you don't fail, you can't succeed.

To be happy, fail. -Me, 2024.

I thought most good intentions are bought up by road construction companies to maintain the highway to hell...