The Pragmatic Programmer
The book that first made "software craftsmanship" feel like a concrete practice rather than a vague slogan. The DRY principle gets quoted everywhere, but the parts about taking ownership and estimating honestly aged just as well.
A Philosophy of Software Design
The clearest argument I've read for why complexity (not bugs) is the real enemy of a long-lived codebase, and why "simple" and "easy to write quickly" are often opposites.
Thinking, Fast and Slow
Not a software book at all, but it changed how I read my own certainty. Understanding how confidently the brain produces wrong answers made me a more careful reviewer of my own decisions, not just other people's code.
The Making of a Manager
Read this well before actually leading anyone, and re-read it after. The gap between the two readings says more about the job than the book itself does.
Deep Work
The book that finally gave me a vocabulary for why a calendar full of "quick syncs" was quietly destroying my ability to think clearly about anything hard.
None of these are framework-specific, and that's exactly why they're still useful years later. The tools change every few years, the underlying problems mostly don't.