It looks like full attention goes to writing code, and none to specification and design, is this correct?
Gian [ February 20, 2007: Message edited by: Gian Franco Casula ]
"Eppur si muove!"
Joined: Jan 23, 2002
Based on the TOC you linked to, it seems to me that the chapters in the section titled "The shape of things to come" might be talking about design. Also, I wouldn't be surprised if the last two sections would cover what I think you refer to with "specification", too.
Of course, I'm just speculating here until Pete responds...
I work out from the codeface (how to write good code - covering things like naming, writing comments, handling errors, and much more) through construction techniques (covering programming tools, how to test, how to debug, how to "build code", coinsidering security, and much more). I talk about the "shape" of code (design, architecture and code evolution). Then the book zooms out to look at programming in the Real World: how to work in teams, review code, write specs and documentation (and when not to!) how to estimate how long it will take to write code. And more.