Friday, February 8, 2008

worse is better.

So I read an article today and I thought wow. Philosophy and Computer Science all rolled into one. Jeff Atwood's blog on worse is better was about Steve Martin book and how Steve Martin talked about not trying to be great, because you will inevitably great for at least one night, but to strive to be consistently good. Then he relates it to how programmers should also strive to be consistently good. This made me think about my programming as well.

It seems that as a undergrad studying computer science, all of my project seems to be my shot at being the best, making the best code that I can possibly write for the best code I can possible get. Now is the whole approach of trying to be great with each project striving to be great once, or trying to be good all the time?

I think that I should not focus so much on trying to write the best code for each project but rather just try to shoot for writing good code consistently. To be honest I really have no idea how to go about this. But it nice to think about for now at the end of the week while waiting for my friend to get out of class so that we can go lift.

Tomorrow I'll be back at work with my 414 project but I'll try to remember to consistently write good code. Whatever that is.

1 comment:

aaron said...

interesting post. to me its about being consistently good on your various tasks. that means don't take shortcuts on design, testing, research, etc. its human nature to focus our efforts on things we already are good in. its also easy for us to get lazy and think we can make it up later.

being good consistently is definitely something i strive for.