3 ms·
But back to laziness. A great programmer is lazy because he or she prefers thinking through a solution to solve a problem rather than hacking through it, which
by swombat 18y ago
But back to laziness. A great programmer is lazy because he or she prefers thinking through a solution to solve a problem rather than hacking through it, which is way too much effort. Dick Vile, a developer I met at FAME Software, a company founded by Larry Rafsky, put it this way: "What do I use to do my programming? A pencil." Thinking things through, coming up with a great design and then doing the coding is the way a real smart, lazy programmer does things.
The article is interesting on the whole, but this point falls flat on its face, in my humble opinion. Some up-front thinking is always required, but aiming to have the whole thing thought through before you start coding is terribly wasteful - if only because you will always get (sometimes quite important) parts of it wrong because non-trivial systems are too complicated to hold in your head in their entirety while creating a new design.
Also, he's only got one third of the picture with laziness. As Larry Wall said, the *three greatest qualities of a programmer are laziness, impatience, and hubris ( http://cranked.me/2008/07/laziness-impatience-hubris-three-great.html http://cranked.me/2008/07/laziness-impatience-hubris-three-g... ).
Humility is in direct contradiction with one of them and in indirect contradiction with another. I personally feel that those are still more important qualities than humility when it comes to being a great programmer - which, I hasten to add, is very different from being a great designer... that requires far more humility.
- Retric 18y agoExperts tend to think though problems until they know they can solve them with the given constraints. This does not mean a 100% upfront solution to all problems but rather an understand where the problems are going to be and how to avoid them. I think the idea of a lazy programmer is someone who avoids early optimization and does whatever will make his job faster at each stage of the process.
- krakensden 18y agoI think more importantly [with regards to humility] that while it's important to talk with your users, you still need to be hubristic. His reason for being humble is this: There is a huge payoff for being humble about your ability to understand software requirements. In Agile methodologies, the goal is to get users a working program as quickly as possible so they can try it and tell you what they really want But you still need to be a bit of an arrogant dictator and remember that just because users tell you what they really want, doesn't mean they really want that. Which doesn't really map to hubris I guess, but it certainly isn't humility. GNOME 2's `draining the swamp' effort comes to mind.