11–20 of 232 posts
I would comment on this issue, but I am still thinking about what the best comment would be....
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 int…
I'm curious to see why something like printf is worth writing in assembly.
In the middle of November, I started a daily (M-F) newsletter on topics related to DevOps. I've been consistent with it ever since.
The strategies the article outlines that have helped me the most are breaking things down into small pieces and starting small.
Also, by making my newsletter daily, it took a lot of pressure off me. I didn't feel like I had to have a "hit" every article like with weekly or monthly cadences. If the article sucked, then tomorrow is a new day with a new article.
“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.
Every self-proclaimed perfectionist should start caring about time as much as they do about the object they are obsessing over. They'll then see the tradeoff in being less of a ^perfectionist^ in that thing and being more ^perfectionist^ about time.
[1] https://www.amazon.com/Procrastination-Why-You-What-About/dp...