>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.

Back in 1997 I was assigned to convert a legacy SAS 5 application to SAS 6.

Let's just say that the original programmer had adopted MANY of the techniques in the linked post. The first thing I did was to go through all the code and convert it to only have one statement per line. eye roll