3 ms·
Ironically, programmers should strive to write the least amount of code as possible, while reading as much code as possible. If we can solve a problem without
by imiric 9y ago
Ironically, programmers should strive to write the least amount of code as possible, while reading as much code as possible.
If we can solve a problem without writing any code at all, then that's the most maintainable and bug free solution.
See "The Best Code is No Code At All": https://blog.codinghorror.com/the-best-code-is-no-code-at-all/ https://blog.codinghorror.com/the-best-code-is-no-code-at-al... .
- schoen 9y agoSee also smr.c from http://www.ioccc.org/years.html#1994 http://www.ioccc.org/years.html#1994 (the world's shortest quine!).
- disgruntledphd2 9y agoThat may be one of the best things I've seen all week.
- kerkeslager 9y agoQuoted for emphasis: > Every new line of code you willingly bring into the world is code that has to be debugged, code that has to be read and understood, code that has to be supported. Every time you write new code, you should do so reluctantly, under duress, because you completely exhausted all your other options. It's worth noting: code you import counts toward your total line count. Don't think that because someone else who doesn't work with you wrote the code, it doesn't count. In some ways, that's worse. I've spent all day today debugging a no-longer-maintained library which is used in a legacy codebase I'm maintaining.