Issue No.06 - November/December (2004 vol.21)
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MS.2004.37
"Clear design is good design" seemed like a reasonable rule of thumb. If you can understand your system, you can change it effectively. If you can't, it's much harder. Sounds simple, right? Maybe a little too simple. Recently, this author has discovered he's periodically sacrificing clarity and subordinating it to another standard.
clear code, testable code, refactoring
Michael Feathers, "Before Clarity", IEEE Software, vol.21, no. 6, pp. 86-88, November/December 2004, doi:10.1109/MS.2004.37