Some professional journals still publish code listings that have such poor layout, variable names, and commenting that they are virtually impossible to read. The code listings contain fundamental programming blunders such as using numeric literals rather than named constants. Professional journals whose code will be read by thousands should take a leadership role in publishing examples of good construction. Researchers, consultants, and writers who dismiss construction as a trivial activity need to realize that construction, by definition, occupies the central role in software development. Analysis and design are done before construction so that construction can be done effectively.
System testing is done after construction to verify that construction has been done effectively.
Construction is at the center of the software-development process. It is where the rubber meets the road, and that makes it a uniquely productive area in which to focus our attentions. Construction is important and will remain so for the foreseeable future. The difference between good and bad construction can mean the difference between project success and failure. The difference between recognizing the key role that construction plays in software development and ignoring it can mean the difference between moving the industry forward and repeating the same old mistakes yet another time.