[Cthulhu_]

I'd say it's still a good resource to have; it's not just about programming but about project management, planning, etc.

I'd take their recommendations about code style and documentation and whatnot with a grain of salt though, languages, tools and styles have changed since then. Don't skip them, but don't adhere to them religiously; add them to your arsenal of knowledge.

It's also a bit of a slog to read front to back, so consider picking one chapter at a time or only looking up a subject you're curious about; I'd consider it more of a reference.

[SideburnsOfDoom]

> I'd take their recommendations about code style ... with a grain of salt though

IIRC, this book started me on the "meta-rules" of code style, the "what makes good rules", specifically

* aim for readability

* the role that "mere familiarity" plays in readability

* Team style over individual style, org over team, industry over org.

* the small amount (but not zero) of actual data i.e. studies here.