«« UnsupportedOperationException First Week »»
blog header image
Hackers and Painters

I just read a great article by Paul Graham entitled Hackers and Painters. There were a lot of great quotes and ideas in it but here are two I liked most:

Everyone by now presumably knows about the danger of premature optimization. I think we should be just as worried about premature design-- deciding too early what a program should do.
When a piece of code is being hacked by three or four different people, no one of whom really owns it, it will end up being like a common-room. It will tend to feel bleak and abandoned, and accumulate cruft. The right way to collaborate, I think, is to divide projects into sharply defined modules, each with a definite owner, and with interfaces between them that are as carefully designed and, if possible, as articulated as programming languages.

His ideas about a loosely typed language allowing for increased changability made sense but I wonder if that wouldn't just increase problems at debugging time instead of compile time. Probably not if you had good tests.

Posted at May 08, 2003 at 09:23 PM EST
Last updated May 08, 2003 at 09:23 PM EST
Comments

If you've read Descartes. Then the second block is really nothing knew. That concept has been around for hundreds for years...probably thousands. It's always best to have the core of the idea and design done by one, and only one person who knows what he/she is doing....you don't wanna have too many cooks in the kitchen.

I often find myself baffled by these "new" ideas. They're not new. It's just people tend to think that Techies are special or something. Meh.

» Posted by: roy at May 8, 2003 11:58 PM

The ideas aren't new but sometimes it's good just to have all of these ideas assembled together and related in an organized way. This article did that well, I think.

» Posted by: Ryan at May 9, 2003 12:48 AM

True dat. We *all* need to be reminded sometimes :-)

» Posted by: roy at May 9, 2003 11:18 AM
Google
 
Search scope: Web ryanlowe.ca