books for programmers

technical (IC track)

heavily focused on backend since frontend patterns are locked by framework.

Clean Code

Robert C. Martin

the handbook everyone references and half actually read. naming, functions, error handling. the basics that separate readable code from clever code.

Clean Architecture

Robert C. Martin

boundaries, dependency rules, the separation that lets you swap frameworks without rewriting everything. read this before your first major refactor.

The Pragmatic Programmer

Hunt & Thomas

the meta-book. not about any language or framework. about how to think like a programmer. DRY, orthogonality, tracer bullets.

Design Patterns

Gang of Four

don't read this cover to cover. watch the playlist instead. implement the ones you need, learn the rest when you hit them in the wild.

Domain-Driven Design Distilled

Vaughn Vernon

the compressed version. bounded contexts, aggregates, ubiquitous language. the thinking tool for systems that are bigger than one person's head.

Cracking the Coding Interview

Gayle Laakmann McDowell

189 programming questions and solutions. the standard prep book. don't memorize — understand the patterns behind the problems. pair it with the video walkthrough.

non-technical

for communicating thought. useful during work and interviews.

The Mythical Man-Month

Fred Brooks

written in 1975, still true. adding people to a late project makes it later. the communication overhead chapter alone is worth it.

The Clean Coder

Robert C. Martin

not about code. about professionalism. saying no, estimating honestly, handling pressure. the book about being a developer, not writing code.

Don't Make Me Think

Steve Krug

UX for people who don't do UX. every programmer should read this. your users aren't reading your interface — they're scanning it.

extra