[readlikeasloth]

This begs the question: what do you recommend instead?

[augustk]

"Code Complete" by Steve McConnell and "A Philosopy of Software Design" by John Ousterhout.

[raverbashing]

I second this about Code Complete. (Also I think it's at its 2nd edition, maybe 3rd?)

It's more up to the point instead of going into dogmatic diatribe

It's more evidence based (giving examples, etc)

Go for this one and Bob's your uncle! (or maybe it stops being your uncle, I guess)

[metaltyphoon]

> "A Philosopy of Software Design"

What a great book. I second this and add my own "The Pragmatic Programmer: 20th anniversary edition"

[h8hawk]

"Structure and interpretation of computer programs", its not exactly in the same category but IMO is far better. At least it doesn't make you write tones of one line,single time used functions with 400 character length name.

[avereveard]

Code complete, Steve McConnell

[mablopoule]

"The pragmatic Programmer" is one I would recommend.

That, and "Team Geek", in term of relationship with codes and teammates.

[JonChesterfield]

The pragmatic programmer is really keen on code generators. Which is the right thing to do. It's also very difficult to do in practice as the languages that are sufficiently impoverished to need external code generators are invariably bound to build tools that can't sanely deal with them.

edit: oh, and also it's hard to avoid people checking in and/or editing the generated code

[CraigJPerry]

Not the OP but HTDPv2 is a solid recommendation here

[asddubs]

I don't understand why you would acronym your book recommendation. Anyone this would be a useful recommendation to would not know about it already, and hence not understand the acronym.

For those wondering, "How to Design Programs"

[CraigJPerry]

Yeah fair comment. I guess i’ve fallen into that familiarity trap.

[tpoacher]

I also enjoyed the Hitchhiker's Tips for Deeper Pockets (v2).

[markeibes]

Programming practice