How to Write Unmaintainable Code (1999)
downbad_
35 points
8 comments
April 03, 2026
Related Discussions
Found 5 related stories in 90.9ms across 8,303 title embeddings via pgvector HNSW
- The unwritten laws of software engineering AntonZ234 · 16 pts · March 17, 2026 · 54% similar
- Clean code in the age of coding agents yanis_t · 49 pts · April 09, 2026 · 54% similar
- Programming Still Sucks jeromechoo · 257 pts · May 06, 2026 · 49% similar
- Refactoring Untested Code kakerane · 11 pts · April 06, 2026 · 48% similar
- Rob Pike’s Rules of Programming (1989) vismit2000 · 901 pts · March 18, 2026 · 48% similar
Discussion Highlights (5 comments)
downbad_
https://news.ycombinator.com/item?id=10237636
none2585
One of my favorites to come back to periodically
oniony
Original: https://www.mindprod.com/jgloss/unmain.html
miqkt
Ah, time to copy this into the custom instructions for an LLM to amuse myself with.
vharuck
>4. Use acronyms to keep the code terse. Real men never define acronyms; they understand them genetically. I'll see this and raise inherited SAS code where data sets in the process were named "AAA", "BBB", and so on. To prevent any kind of naming reason, even chronological, new data sets could adopt others' when the existing data set would no longer show up in the program. Which was so helpful when updates needed the previous data.