A nice blog post for levels of making code work was brought to my attention. Here is a quick reminder cheatlist:
- Make it work
- Make it work well
- Make it work automatically
- 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 Proccessing.org:
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. – http://developers.slashdot.org/story/14/01/21/1847217/code-is-not-literature
See also: