Fast to build, slow to trust: the durability backlash
'The Slow Formation of Durable Software' (49980346) hit a nerve. One commenter said they had scrapped entire projects because AI made adding a feature seem easy, and it is 'very difficult to vibe code and not add a bunch of useless crap features.' Another conceded that nobody can work slowly anymore, because everyone expects development to be instant. In the 'Push ifs up and fors down' thread (49997073), the top comment complained that LLMs turn trivial ideas into long, obtuse posts with needless analogies, and others asked for benchmarks that were never provided.
The pattern: cheap output has moved the scarce resource from typing to judgment. What to cut, what to keep, and what to measure are now the hard parts, and people see their own tools failing at them.
The counterpoint is a 60-year-old developer in an older thread (47282777) saying Claude Code reignited his passion. The speed is real and fun, but it needs a human saying no.
So what?
Your edge is restraint. Ship fewer features, write down what you refuse to build, and tie code-structure claims to measurements. Teams that treat 'it was easy to add' as a reason to add will pile up surface area they cannot support.