SE-UA Net resource atlas
A short row of technical books on a plain shelf with a notebook beside them

Technical books

The book is still the cheapest way to learn a technical topic in depth. A web search will get you to an answer quickly. A book will get you to an understanding slowly, and the understanding is the part that pays back over years. This page is a short shelf, not a catalogue.

For a topic-specific entry, see the Pyrobooks technical reading notes.

How to pick a technical book

Three quick checks save a lot of bad purchases:

  1. Read the table of contents. If it looks like a course you would actually take, that is a good sign.
  2. Read one full chapter from the middle, not the introduction. The introduction is usually the part the author wrote last and most carefully.
  3. Look at how the book handles a topic you already know. If the explanation is honest about the awkward parts, the rest of the book is likely honest too.

Topic areas covered in the library

Reading habits

A technical book read with a notebook open is worth several read without one. The notebook does not need to be elaborate: a page per chapter, the open questions you still have, the part you intend to try on the bench, and the part you disagreed with. The disagreement is often the most useful entry, because it is where the book meets your actual experience.

A second pass through a difficult book a year later is also unusually high-value. The book has not changed, but you have. The chapters that were opaque the first time are often the most useful the second time.

Common mistakes

  • buying a book on a topic you are not yet practising
  • collecting books faster than you read them
  • reading the introduction and giving up
  • refusing to mark up the book

Where to go next

Two-minute checklist

  1. Read a middle chapter before buying.
  2. Read with a notebook open.
  3. Mark up the book.
  4. Re-read the difficult chapters after a year of practice.
  5. Pair every book with one bench session.