4 ms·

This completely contradicts what I was taught about being a lazy programmer. Laziness, to me, means that you only type the code that you need to (essentially t

This completely contradicts what I was taught about being a lazy programmer. Laziness, to me, means that you only type the code that you need to (essentially the DRY principal, Don't Repeat Yourself.) Beginner programmers are 'eager', they want to continually pound the keyboard until the program does what they want it to do. Lazy (senior?) programmers carefully decide each line of code that gets included, because they don't want to have to repeat themselves or throw out code that wasted their time. Maybe someone can clarify my thoughts better. But being lazy does not mean waiting to code until you have the entire idea in your head. Programmers who do that typically miss the mark of what their users want.

maurycy 18y ago
Mostly yes. The another thing that can be added to your last paragraph is that frequently the code speaks for itself, and suggests you solutions to the problems.
raju 18y ago
Again, mostly yes. Another way I look at a "lazy programmer" is in the way of how a developer works. If a "lazy" developer has to do the same thing 3 times, then they will figure out a way to automate it. A "lazy" developer also tries to find the best tools for every job, and figures out how to best leverage those tools for maximum productivity and least effort. Whether it be the right language for a task at hand, to using macros and powerful editors (to perform "surgery" on text [I quote Yegge here]) to learning keyboard shortcuts for their IDE of choice so to minimize hand movements etc. This also applies itself to not violating DRY, to thinking about higher level of abstractions so as to reuse code better, writing modular functions that are easily accessible and do not violate the Principle of Least Surprise. I know I am missing a lot here, but in conclusion, I agree with you about the article.

maurycy 18y ago

Mostly yes. The another thing that can be added to your last paragraph is that frequently the code speaks for itself, and suggests you solutions to the problems.

raju 18y ago

Again, mostly yes. Another way I look at a "lazy programmer" is in the way of how a developer works. If a "lazy" developer has to do the same thing 3 times, then they will figure out a way to automate it. A "lazy" developer also tries to find the best tools for every job, and figures out how to best leverage those tools for maximum productivity and least effort. Whether it be the right language for a task at hand, to using macros and powerful editors (to perform "surgery" on text [I quote Yegge here]) to learning keyboard shortcuts for their IDE of choice so to minimize hand movements etc. This also applies itself to not violating DRY, to thinking about higher level of abstractions so as to reuse code better, writing modular functions that are easily accessible and do not violate the Principle of Least Surprise. I know I am missing a lot here, but in conclusion, I agree with you about the article.