Notes On Software Design

Oct 17, 2012

It’s up to me to direct the software that I write. It’s easy for me to forget that. It’s also easy to just jump into a code base and make a quick change because it’s, well, quick.

Today I was after a small change. Easy enough. I just needed to add a an additional check to an if/else statement. First thought was to simply add an or to the statement. But then that little voice in my head reminded me of all of the times that one additional check turned into 3, 4, or 10.

I decided to pull that code out into a new class. Now as the requirements change, the class can handle it. I knew it was the right thing to do, even though it took longer than adding an or to the statement. I decided to design that code the way I thought it should be designed.

It’s my job to drive the software. I dictate how long something takes. I dictate how something should be built. And I dictate when something is finished. Software design means a lot.

If you enjoyed this and would like to be notified the next time I write something, you can subscribe with your choice of RSS or Email.

I promise not to spam you and you can unsubscribe at anytime.

Also, here are some other items you might like longer longer:

or go see everything in the archive.