How to Write Unmaintainable Code (1999)
downbad_
35 points
8 comments
April 03, 2026
Related Discussions
Found 5 related stories in 33.3ms across 3,471 title embeddings via pgvector HNSW
- The unwritten laws of software engineering AntonZ234 · 16 pts · March 17, 2026 · 54% similar
- Rob Pike’s Rules of Programming (1989) vismit2000 · 901 pts · March 18, 2026 · 48% similar
- The Three Pillars of JavaScript Bloat onlyspaceghost · 117 pts · March 22, 2026 · 47% similar
- If you thought code writing speed was your problem you have bigger problems mooreds · 306 pts · March 17, 2026 · 46% similar
- LLM Doesn't Write Correct Code. It Writes Plausible Code pretext · 62 pts · March 07, 2026 · 46% 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.