Friday, August 26, 2005

Lazy for Programmers, sure but Dumb?

This is in reply for this article.

Ok it's kind of compelling the reasons to keep things easy. Don't overthink items. Never assume. But the poster keeps using the words "stupid" and "dumb" to convey this attitude.

I disagree, and would suggest a different set of words: rustic and simple.

Being rustic isn't a bad thing. It's keeping things simple and taking the straightest path to the solution. Don't worry about fixing the barn doors when the barn's on fire. Simplicity is the act and art of not trying to show-off that you're greater than anyone else and how cool you can make things.

Look at quaker furniture. It's not sought after because it's got so many new-fangled features. It's simple, solidly made work. It does what it does and can't be also used as a cappucino machine. Sure they are put cleverly together, but people easily overlook that (kind of like how cleverly the start page is put together).

The rest of article makes sense. Go for the low hanging fruit and when there aren't anymore, maybe you shouldn't start straining for the higher ones. But I imagine people trying to get "dumber" in programming and I just don't feel it can be a good thing when people really should trying to solve something simply and cleverly.

No comments: