Learn To Evaluate Your Code

Word Count: 222
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 :)

Comments

#1 Posted By: Peter Bell Posted On: 1/23/07 10:45 AM
Hey Dan,

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 Posted By: Dan Posted On: 1/23/07 10:58 AM |
Author Comment
Peter,
I have come to learn that there is nothing wrong with asking others for help.
#3 Posted By: Peter Bell Posted On: 1/23/07 11:06 AM
That is for sure! One of the main reasons I blog is to get input from others.
#4 Posted By: Mark Drew Posted On: 1/23/07 12:01 PM
I just got this book thanks to the guys that made FusionDebug, and its next on my reading list... I love the head-first books... real neat stuff!
#5 Posted By: Dan Posted On: 1/23/07 12:11 PM |
Author Comment
You are really going to enjoy this book. I used to think that to become a better programming I had to see how others code and coding examples from what is "the right way" to do it. While this approach may help you when you are first learning it is not the way to go. You really need to understand how things work and best practices help you achieve this. While this book will give you 0 ColdFusion code it really helps you to think analyze a problem and break down your requirements into real world objects. If you are reading this and do not have this book, even half way through I would highly recommend this book to anyone.
#6 Posted By: Ben Nadel Posted On: 1/23/07 12:30 PM
I am making my way through it slowly - just finished the first chapter this morning on the train (its been a hard month). But so far really liking it. The one thing that I really didn't like was that the Guitar search in the first chapter doesn't use Price Range. That seems like a very real world situation and something that would completely not jive with the GuitarSpec approach they are using for search. .... but anway, I am just starting Chapter 2, so who knows where they go with this :)

So far, though, I am liking it a lot.
#7 Posted By: Dan Posted On: 1/23/07 12:36 PM |
Author Comment
Ben,
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 Posted By: Ben Nadel Posted On: 1/23/07 12:46 PM
Hella Sweeeeeet! That's what I was hoping for :D


Post Your Comment

Leave this field empty







Show Captcha

If you subscribe, any new posts to this thread will be sent to your email address.

Copyright © 2007 Dan Vega | BlogCFC was created by Raymond Camden. This blog is running version 5.8.001.