feat: polish slow-is-smooth-smooth-is-fast

Author: MyNameIsTrez

_posts/2026-05-22-slow-is-smooth-smooth-is-fast

@@ -4,14 +4,15 @@ title: "slow is smooth, smooth is fast"
 date: 2026-05-21 12:00:00 +0100
 ---
 
-I think a lot of low quality code gets written when programmers rush themselves, instead of taking plenty of time to consider all options. Quite often programmers feel more rushed than they actually are, because they feel embarrassed if they spend more time than they would like.
+I think a lot of low quality code gets written when programmers rush themselves, rather than taking plenty of time to consider all options. I personally think programmers often feel more rushed than they actually are, because they feel embarrassed if they spend more time on something than they would like.
 
-I think most programmers are totally capable of writing superb quality code, if they just allowed themselves to slow down. Of course this is different for companies with toxic work cultures, but I truly believe a minority of all programmers work at such companies. The term "10x programmer" becoming popular also unfortunately really reinforced this idea of speed being the end-all goal, even for hobbyists.
+I think most programmers are totally capable of consistently writing superb quality code, if they just allowed themselves to slow down. Of course this is different for companies with toxic work cultures, but I truly believe a minority of all programmers work at such companies. The term "10x programmer" becoming popular also unfortunately really reinforced this idea of speed being the end-all goal, even for hobbyists.
 
 I don't think I've ever heard anyone talk about this embarrassment factor in any of the programming blog posts I read and videos I watched over the past decade.
 
-The expectation at any company to estimate how long something will take also reinforces the idea that it matters how much time a person spends on something.
-I know that companies have to turn a profit, but ultimately a lot of codebases and companies would be better off if they got 1 superbly polished feature in a year, rather than 3 mediocre ones. But in my experience, not that much total time is lost anyways when I take my time: reviewers can review it quicker, we have less back-and-forths, and less bugs that have to be fixed later are introduced.
+The expectation at almost any company to estimate how long something will take also heavily reinforces the idea that it matters how much time a person spends on something.
 
-I think the only thing that can be done is to tell colleagues and people online that you should not feel embarrassed and a worse programmer for taking your sweet ass time to deliver code:
+I know that companies have to turn a profit, but ultimately a lot of codebases and companies would be better off if they got 1 superbly polished feature in a year, rather than 3 mediocre ones. In my experience though, not that much total time is lost anyways when I take my time: reviewers can review it quicker, we have less back-and-forths, and barely any bugs get introduced that have to be fixed later.
+
+The only thing we can do is remind colleagues and people online that taking your sweet-ass time to deliver code doesn’t make you a bad programmer:
 > [slow is smooth, smooth is fast](<https://en.wiktionary.org/wiki/slow_is_smooth,_smooth_is_fast>)