THE READING ROOM / BOOK GUIDE
Coders at Work
Peter Seibel interviews fifteen programmers about how they learned, what they build, and where the craft resists easy explanation. The talk is practical, opinionated and grounded in decades of work.
About the book
Coders at Work collects long-form conversations between Peter Seibel and fifteen working programmers. The subjects span language design, systems programming and software tooling, and each talks at length about training, debugging, design taste and the habits that accumulate over a career. Seibel asks about origins and influences, then pushes into specifics: how a particular problem was approached, what tools were used, what went wrong.
The format matters. These are interviews, so the book's substance arrives through back-and-forth. Readers get competing accounts of the same questions, and disagreements surface without a referee smoothing them over. Seibel's questions are informed enough to follow technical detail and plain enough to keep the conversation moving. The result reads as a set of portraits of how programmers think.
How to read it
Approach it as a collection. The interviews stand alone, and dipping into the ones whose subjects you already know is a reasonable way to test whether the format suits you. The technical passages assume some familiarity with programming, though Seibel generally supplies context when a subject names a language or system.
Pay attention to where the interviewees disagree. Advice about education, code review, testing and tooling varies considerably, and that variety is the point. Read for the reasoning behind each position. The conversational pace is brisk, but the density rises in discussions of language design and low-level systems work.
Who it suits
Programmers early in a career will find useful perspective on how skill develops and how experienced practitioners describe their own mistakes. Readers with several years of work behind them may recognize their own habits in the interviews and get more from the technical exchanges. Anyone interested in the culture of software development around the 2000s will find a candid record of how practitioners talked about their field.
Reading considerations
The tools, languages and working conditions discussed belong to the period in which the interviews were conducted. Some subjects are well known and others less so, and the selection shapes the picture of the field considerably. Readers looking for a systematic textbook or a single coherent method will not find one here; the value lies in the range of individual testimony.
Follow the HN conversation
126 different recommenders are recorded in the upstream dataset. These are AI-classified source counts, not an independent rating.
Search HN comments about this book ↗
Explore videos on the same subject ↗
Book notes prepared with DeepSeek, using catalogue records and Open Library subject information. They are reading guidance, not a personal review or a verified chapter-by-chapter account. Book details can vary by edition. HN data methodology · Book metadata and covers.
