How to Write Unmaintainable Code (1999)
32 points
4 hours ago
| 5 comments
| doc.ic.ac.uk
| HN
vharuck
1 hour ago
[-]
>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.

reply
oniony
4 hours ago
[-]
reply
downbad_
4 hours ago
[-]
reply
mitchbob
4 hours ago
[-]
reply
miqkt
4 hours ago
[-]
Ah, time to copy this into the custom instructions for an LLM to amuse myself with.
reply
seamossfet
3 hours ago
[-]
Honestly, it'd be really funny to try and make a CLAUDE.md file for slop maxxing.
reply
Blackarea
2 hours ago
[-]
Could make that an AGENT.md and use a dumber model via opencode to slop maxx even harder!
reply
none2585
4 hours ago
[-]
One of my favorites to come back to periodically
reply