Reducing Assumptions, Exploding Your Code
mpweiher
30 points
10 comments
July 05, 2026
Related Discussions
Found 5 related stories in 504.9ms across 14,015 title embeddings via pgvector HNSW
- With Claude: Less Coding, More Testing ingve · 22 pts · May 31, 2026 · 54% similar
- Test-case reducers are underappreciated debugging tools ltratt · 108 pts · June 09, 2026 · 52% similar
- Quadrupling code performance with a "useless" if birdculture · 107 pts · July 13, 2026 · 52% similar
- Throwing away 18 months of code and starting over tomaspiaggio12 · 46 pts · March 10, 2026 · 52% similar
- Refactoring Untested Code kakerane · 11 pts · April 06, 2026 · 52% similar
Discussion Highlights (3 comments)
middayc
I'm the author. If anyone has any feedback, you are welcome ...
tananan
I generally work on internal-use Python codebases. I would much rather do some basic validation and fail loudly if anything I didn’t account for happens. One of the issues I run into is that agents are predisposed to write extremely defensive, odd-case-handling code, and that makes me recoil when I have to look into it: the SNR ratio is very low. You get a spaghetti that is unlikely to crash, but really hard to extract the gist of. And finding more global bugs can be difficult because what should be structural impossibilities can be coerced into silent skips. The article made me think that maybe what I’d like is a language where validation doesn’t triple the lines of code you have to write.
mike_hock
Yeah, or just let the exceptions bubble up and the boilerplate goes away.