> 1) Make your code as terse and dense as possible so you can see as much of it at one time as possible (see code written by Arthur Whitney). Why? I don't want

> 1) Make your code as terse and dense as possible so you can see as much of it at one time as possible (see code written by Arthur Whitney). Why? I don't want to see as much code as possible. I want to see the code I'm interested in. If I can read 4 lines of code and understand what it does, I spend less time and energy than reading 20 lines of code and trying to reverse engineer it. > 2) Make your variable names abbrevations or acronyms, like instead of 'convertInt', call it 'ci'. That makes no sense, it's gross and has only drawbacks. > 3) Comment every function and keep each function to only a couple lines. So you need one or more comments for two lines of code? > 4) Because your functions are so small and dense, you'll never need to modify them, only throw them away. If you're only writing them to throw them away, why not optimize and never write them in the first place? > 5) Bam, your comments and never out of date because the functions you're writing never need to be modified, only deleted. This is sarcasm, right? I feel like I've been trolled.