I am in the middle of reading a new book from the Head First series titled
Object-Oriented Analysis & Design. I am on part 2 of chapter 5, good design = flexible software. There is a very important paragraph in this chapter that I would like to share with you. If you are reading along at home we are on page 246.
It's easy to rip apart someone else's code, but you've got to learn to look at your own code, and identify problems. This is also where peer review, having fellow programmers look at your code, can really be a lifesaver. Don't worry if you have to make changes; a better-designed application will save you tons of time in the long run.
When I read this I could not help but think how many times throughout a week or month that I have ripped apart others code criticizing how others accomplish a task. I think we should all take a little more time criticizing ourselves because if you really take the time to do so you will realize what I have, nobody is perfect :)
This entry was posted on January 23, 2007 at 10:20 AM and has received 1129 views. Comments 8 |
Print this entry.
#1 by Peter Bell on 1/23/07 - 10:45 AM
Don't fel like you have to rip apart your code. Just post it on the blog and we'll all rip it apart for you :D
#2 by Dan on 1/23/07 - 10:58 AM
I have come to learn that there is nothing wrong with asking others for help.
#3 by Peter Bell on 1/23/07 - 11:06 AM
#4 by Mark Drew on 1/23/07 - 12:01 PM
#5 by Dan on 1/23/07 - 12:11 PM
#6 by Ben Nadel on 1/23/07 - 12:30 PM
So far, though, I am liking it a lot.
#7 by Dan on 1/23/07 - 12:36 PM
The guitar search design is not very flexible for a reason. As you make your way through the book they improve on it and everything will make more sense soon.
#8 by Ben Nadel on 1/23/07 - 12:46 PM