style: cut redundant claim about low quality code

Author: MyNameIsTrez

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

@@ -6,7 +6,7 @@ date: 2026-05-21 12:00:00 +0100
 
 [Slow is smooth, smooth is fast](https://en.wiktionary.org/wiki/slow_is_smooth,_smooth_is_fast) is a neat phrase, but it is usually explained backwards. People say: go slow, avoid mistakes, save time overall. That is true but it misses where the urge to rush actually comes from.
 
-A lot of low quality code gets written when programmers rush themselves. The rush is mostly self-imposed, driven by embarrassment at spending longer than expected on something. Everyone talks about external pressure: deadlines, sprint velocity, manager expectations. The internal pressure gets ignored.
+The rush is mostly self-imposed, driven by embarrassment at spending longer than expected on something. Everyone talks about external pressure: deadlines, sprint velocity, manager expectations. The internal pressure gets ignored.
 
 That embarrassment is not about the work taking long; it is about feeling like the time reflects on you rather than on the problem. You imagine a faster version of yourself who would have finished by now. Time estimates make this worse, reinforcing the idea that how long you spend is a measure of your ability rather than a fact about the problem's difficulty.