Hale
WritingMarch 24, 20269 min read

The Thursday Reading Group

For two years we read one paper or essay a week, out loud, with a hard stop. It changed how the team argued more than any offsite.

By Julian Hale · Portland, Oregon

Empty wooden chairs around a low table stacked with books and a teapot.

The format was stubborn. Thursday, thirty-five minutes, cameras on if you could. Someone read a section aloud. We did not summarize for people who had not read. We did not allow laptops except for the text. At minute thirty-five we stopped, even mid-sentence. The unfinished feeling was the point. It sent people back to the page.

We read old things on purpose. Brooks. Weinberg. A chapter from *The Design of Everyday Things*. A paper on crash-only software. The occasional agent paper, treated with the same suspicion as the rest. New work is allowed, but it has to survive contact with people who have been thinking about systems since before the current names existed.

What it did to argument

Teams argue with slogans when they do not share texts. After a year we had a small private language that was not jargon. Someone could say “this is a sign, not a handle” and we would know. Someone could say “we are optimizing the anecdote” and the meeting would turn. That is cheaper than another framework.

  • One piece, not a syllabus. Depth over coverage.
  • Read aloud. It slows the confident and includes the quiet.
  • No slides. If it needs a slide, it is a talk, not a reading.
  • Hard stop. Respect is a clock, not a feeling.

If you start one, resist the urge to make it useful. Usefulness arrives later, sideways, in a design review you did not plan. The hour itself should feel slightly impractical. That is how you know it is not another meeting in costume.

Letters on this piece

  • Leila Brooks · March 25, 2026

    We stole this format. The hard stop is surprisingly emotional. People linger in the hallway, which I think is the actual meeting.