Wednesday, 1 February, 2006
In his article, “Making Wrong Code Look Wrong”, Joel discusses the idea that besides having some style, whatever it might be, a key to good programming is to engineer the conventions for a project so that wrong things look wrong. This can be done by organizing code so that the main consequences of a line of code, and the semantics of the line of code, are visible locally, without having to search around the program to see what’s really going on.


