style: mention programming videos, and say "never"

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 I think the reason it's true is rarely spelled out.
 
-A lot of low quality code gets written when programmers rush themselves, and 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, I've rarely seen this named. Everyone talks about external pressure: deadlines, sprint velocity, manager expectations. The internal pressure gets ignored.
+A lot of low quality code gets written when programmers rush themselves, and 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 programming videos, I've *never* seen this 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 for craft. Time estimates make this worse, reinforcing the idea that how long you spend on something is a measure of your ability rather than a property of the problem.