Recommended reads for teams that think deeply about their work

Not everything worth reading is about software.

Some of the ideas that have shaped how we work came from places far outside our industry: books about architecture, essays about craft, interviews with people who have nothing to do with technology but everything to do with doing good work. Over the years we've collected the ones that stuck, and we share them with new team members often enough that it felt worth writing them down.

This isn't a definitive list. It's just the handful we keep coming back to.

On building things that last

The best products, like the best buildings, are designed to age well. They're built by people who thought about the person on the other end, often years into the future.

What we've taken from this is a simple reframe: stop asking "does this work" and start asking "will this still feel right in three years." It's a higher bar, and it changes the decisions you make. The features you'd add for a quick win look different when you imagine living with them for a long time.

Good work is what's left after you remove everything that was only there to impress.

On focus and attention

There's a quiet theme running through almost everything we admire: the people who do remarkable work tend to do fewer things, more deeply.

It sounds obvious, and yet the pull in the other direction is constant. There's always one more feature, one more channel, one more opportunity that seems too good to pass up. The teams we respect most are the ones that have made peace with saying no, not because they lack ambition, but because they understand that depth is a choice you make at the cost of breadth.

A few ideas we return to on this theme:

• That the cost of any commitment is everything else you could have done with that time

• That the quality of your work is shaped more by what you decline than what you accept

• That attention, not time, is the real scarce resource

• That the hardest discipline is protecting the work that merely feels urgent

On craft for its own sake

Some of the most useful lessons come from people who care about details that no one will ever consciously notice.

A typographer obsessing over the space between letters. A chef refining a dish no critic will ever fully appreciate. A musician spending hours on a passage most listeners will hear once. There's something in that level of care that translates directly to building software: the belief that the details matter even when, especially when, they go unseen.

We've found that the teams who care about the invisible details tend to produce work that simply feels better, in ways users can sense but rarely articulate. That feeling is the accumulation of a thousand small decisions made by people who cared.

On staying curious

The last thread is the simplest: the people who keep growing are the ones who stay curious well past the point where they could coast.

It's easy, once you're good at something, to stop learning and start repeating. The reads we value most are the ones that resist that, the ones that remind us there's always another level, another perspective, another way of seeing the thing we thought we understood.

A small invitation

We share these not because they're the "right" books or essays, but because they shaped us, and because the best conversations we have with other teams often start with "have you read..."

So consider this an open invitation. If something here resonates, or if there's something you think we should be reading, we'd genuinely love to hear it.