TITLE: Different Kinds of Lazy and Dumb
AUTHOR: Eugene Wallingford
DATE: May 09, 2006 5:07 PM
Sometime in the last month, I came across a link to an
article that is a couple of years old,
Why Good Programmers Are Lazy and Dumb.
I like to read that kind of article every once in a while,
even if I've seen the general ideas before. Usually, such
an article hits me in a particular way according to my
current frame of mind. Here are the ideas that stood out
for me this weekend:
Just as it's true that if you can't handle the
right kind of pain
you'll have a hard time getting better at much of anything,
it's true that if you can't find the balance between the
rights kind of lazy and dumb, you'll have a hard time
taking your skills to the next level.
- Balance. Without it, we usually go astray.
- Lazy? "... because only lazy programmers will want to
write the kind of tools that might replace them in the
But you can't be so lazy that you are unwilling to
write those tools, or to refactor your code, to save
time in the future. You have to be forward-thinking
You Aren't Gonna Need It
is an admonition against doing work too soon. But sometimes,
you do need it.
- Dumb? "The less you know, the more radical will your
approaches become...." You know,
and all that.
But you can't be so dumb that you don't have the raw
material out of which to propose a radical solution.
You can only think outside the box when
you start with a box.