What is "good code"?

I was asked today to describe "good code".  Here is my response to that question:

How do you define “good code”?


“Good code” is code that functions. “Good code” is code that does what it’s supposed to do. After all, with so many applications in production, can most of that code be below average or “bad code”? However I am not interested in writing “good code”. I am interested in writing great code. I like writing code that does what it’s supposed to do and reads like it’s supposed to read. Great code does not make the reader ask “WTF?!” when reading it. Great code is code that all programmers aspire to write in their careers but only a persistent few ever do.

Great code is based on the concepts that universities teach but professors fail to teach you how. Great code is code that is loosely coupled, highly cohesive, highly readable and as a result highly maintainable. Great code is that which is appreciated more by the developer that maintains it, than the one who created it. The skill of writing great code does not come from talent, intelligence or experience but rather from practice with a deliberate attempt to learn how to write it.

Great code is not plagued by duplication. Great code is efficient. Great code is open for extension. Great code has clear separation of concerns. Great code has clear names for functions, class names and variables. Great code has small classes and small functions (methods). Great code avoids magic numbers. Great code is pronounceable. Great code has classes and methods that do one thing and do it well. Great code is so expressive that comments are rarely necessary to explain it. Great code utilizes design patterns to solve re-ocurring problems. Great code reveals the domain.

Great code is clean. Great code is concise. Great code is testable and tested. Great code is easily recognized by all developers and sometimes even referred to as “sexy” by the committed developers. Great code makes a programmer proud and not shameful.

I can go on and on about what “great code” is, after all code is my passion, but the one thing that I would like to point out is that great code is studied, researched and practiced by all those who care about code and I happen to be one of those aspiring craftsmen.

Also I cannot say all of this without giving credit to all of those masters of great code that have shared their knowledge of great code through teachings, seminars, articles, books, podcasts,user groups, etc. I am referring to the Martin Fowlers, Michael Feathers, Robert Martins, Steve McConnells, Eric Evans, Jeremy Millers, Jeffrey Palermos, Derick Bailey’s of the world. The list of great contributors is almost as long as the list of attributes of great code, so I will not attempt to name them all. Instead I just want to say thanks for their inspiration of writing great code.

Comments

Unknown said…
Fernando although I am not a programmer I can appreciate your passion for your craft. Hopefully this passion becomes infectious and permeates throughout our organization.
August 18, 2010 at 4:24 AM
Derek Greer said…
Great post Fernando! Keep 'em coming.
August 18, 2010 at 5:07 AM
Post a Comment

Popular posts from this blog

Simple Example of Using Pipes with C#

Image
So I decided to dig into understanding how Asp.net works under the hood, out of curiosity.  In the articles that I found the authors described the architecture in lower level details.  One of the things that caught my eyes was the use of named Pipes as a means of inter-process communications by the architecture.   So I decided to dig into that portion a little bit deeper.  I discovered that the .Net framework has a namespace for named pipes and it's quite easy to use. I intend to demonstrate a small example that I cooked up rather quickly by setting up a named pipe server and then connecting a pipe client to it.  Before I do that, I want to say as a disclaimer that I don't know that this example demonstrates the best way to use pipes.  What it does do is show the most straightforward way to use them.  Also, before you use pipes you should consider using something else like WCF instead if you need well defined interfaces, as using pipes is pretty raw.   Being the type of perso
Read more

Putting Files on the Rackspace File Cloud

Recently, I’ve been playing around with Asp.Net MVC and I (along with some friends) am creating an Asp.Net MVC application that can access files from our website. This means that files must display on the site as well as provide a way to download/upload them. I won’t give away all the details of the project but I will say this: Sharing photos is one of the driving forces for our project.  The files are only image type files( jpg, etc) The files must be uploaded by the users and stored somewhere within our system.  We don’t necessarily know at this time how much storage space we need but we think that we will need a little at first but possibly a lot more down the road. This means that the storage of these files must be scalable. The uploading of files must be controlled by our system.  Right off the bat we started our application and were uploading files to the web server with no problem.  We only did it this way to kind of prove our system model. We were just basically writing
Read more

Why I Hate Regular Expressions

I have a love-hate relationship with regular expressions.  I admire their power yet I hate the pain and agony they have caused on more than one occasion. Just recently one of my colleagues used a regular expression for validating passwords. It seems pretty fair to use regular expressions for validating character sequence patterns. After all it seems they were created exactly for that.  However when regular expressions fail they fail hard.  What I mean by that is that they usually fail in the production environment. In case you are wondering what a regular expression is take a look at the wikipedia explanation of regular expressions . So we go live and all of a sudden new users can't be created because the regular expression says that the password is not valid due to one of the complexity rules.  But how?  The regular expression passed all the unit tests.  In fact the application works fine in our development and test deployment.  So what happened? The validation works fine unti
Read more