style: tighten embarrassment factor paragraph

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
 
 I think a lot of low quality code gets written when programmers rush themselves, rather than taking plenty of time to consider all options. And I think the rush is mostly self-imposed, driven by a kind of hidden embarrassment at spending longer than expected on something.
 
-In a decade of reading programming blogs and watching videos, I've almost never seen anyone specifically call out this embarrassment factor. Everyone talks about external pressure: deadlines, sprint velocity, manager expectations. The internal pressure gets ignored.
+In a decade of reading programming blogs, I've rarely seen this embarrassment factor named. Everyone talks about external pressure: deadlines, sprint velocity, manager expectations. The internal pressure gets ignored.
 
 It works like this: you see a colleague close tickets quickly and assume that speed is what competence looks like, so you start optimising for looking fast rather than being good. The time estimates almost every company demands from programmers make this worse, reinforcing the idea that how long you spend on something is a measure of your ability.