style: move embarrassment factor paragraph up

Author: MyNameIsTrez

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

@@ -6,10 +6,10 @@ date: 2026-05-21 12:00:00 +0100
 
 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 consistently writing superb quality code, if they just allowed themselves to slow down. Of course this is different for companies with toxic "10x programmer" work cultures, but those should be avoided anyways.
-
 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.
 
+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 "10x programmer" work cultures, but those should be avoided anyways.
+
 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 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.