I agree with the sentiment, but calling this "Lazy" isn't correct. Truly lazy programmers do things like not understanding the requirements first, sloppily copy-pasting code, failing to write any kind of tests, or even failing to test it once themselves. The truly lazy programmer alos make no attempt at generalization, or comparing to existing code.
I agree with the sentiment, but calling this "Lazy" isn't correct. Truly lazy programmers do things like not understanding the requirements first, sloppily copy-pasting code, failing to write any kind of tests, or even failing to test it once themselves. The truly lazy programmer alos make no attempt at generalization, or comparing to existing code.
I agree that it can be misinterpreted to call it "Lazy", but hopefully the idea is clear after reading the post. Thanks for pointing it out!