The book of inspiration

May 26, 2009

Code maturity

Filed under: life — Tags: , , , , — zproxy @ 11:22 am

A nice blog post for levels of making code work was brought to my attention. Here is a quick reminder cheatlist:

  1. Make it work
  2. Make it work well
  3. Make it work automatically
  4. Make it work invisibly

[…] “Good enough” is a programming concept that varies a lot from project to project, but overall it broadly fits into four categories.  Understand which one you’re aiming for and whether it might be useful to try to progress your code to a higher level of “Good enough”.

I have already posted about code quality earlier.

Update: A quoute from

The argument is not to avoid continually rewriting, but rather to delay engineering work until it’s appropriate


[…] That fact that the code performs it’s function is the first economic value of the code. But an equally large, and perhaps greater economic value (or cost) is how well another human can read and comprehend that code later on when managers decide to add pointless features or remove useful features.
Most code is written for economic reasons of some type. Writing code for another human to easily comprehend later increases the economic value of that code — possibly greatly. –


See also:



  1. Thanks for the mention, man.

    Keep in touch!

    Comment by Adam Tal — July 5, 2011 @ 6:26 pm

  2. I will! 🙂

    Comment by zproxy — July 11, 2011 @ 8:26 am

RSS feed for comments on this post.

Sorry, the comment form is closed at this time.

Create a free website or blog at

%d bloggers like this: