This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Before Clarity
November/December 2004 (vol. 21 no. 6)
pp. 86-88
"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.
Index Terms:
clear code, testable code, refactoring
Citation:
Michael Feathers, "Before Clarity," IEEE Software, vol. 21, no. 6, pp. 86-88, Nov.-Dec. 2004, doi:10.1109/MS.2004.37
Usage of this product signifies your acceptance of the Terms of Use.