|laziness, impatience, and hubris|
Code Complete ++
The second book that I would recommend is "Practical Software Maintenance" by T. M. Pigoski. My (limited) experience is that, while most methodology books focus on creating new stuff, most programming revolves around maintaining existing stuff-- apparently maintenance isn't a very sexy topic for authors. I guess that must I disagree with most methodology book authors as I tend to think that knowing how to maintain something well should be a prerequisite for being allowed to design something new.
The third book that I'd recommend is, errr, hmmm, I don't really have a third recommendation.
I seriously enjoy book shopping, but yeah, don't buy the books if you aren't going to read them (not that I've read all the books that I've bought, just most of the non-reference ones). Hmmm,
In reply to Re^2: Software design -- The confussion of buzzwords