Writing

Shorter thoughts on leading through the AI era, building businesses, and what I’m noticing along the way. The bigger work is under Stories, and things I’ve built are under Making.

On this site

  1. Building tools for my own team Why I spend some of my week building small tools for the people I work with, and what I've learned from shipping them.

On the thoughtbot blog

Each links to the original.

  1. When to vibe code an app and when to hire someone Vibe coding is a great way to prototype an app. Here’s when to bring in professional developers. ·thoughtbot blog ↗
  2. Don’t hire thoughtbot to write code AI makes code faster and cheaper to produce. Premium consultancies need to offer experienced judgment and help teams solve the right problems. ·thoughtbot blog ↗
  3. AI makes creating software faster, but in regulated industries, judgment matters more Regulated industries face a harder challenge, moving faster without increasing risk. ·thoughtbot blog ↗
  4. A prototype is not a product. It’s a conversation. The best prototypes aren’t built to validate software. They’re built to create alignment. ·thoughtbot blog ↗
  5. Why thoughtbot is joining the Ruby Alliance A coalition of companies investing in the long-term sustainability of Ruby infrastructure. ·with Chad Pytel·thoughtbot blog ↗
  6. How to launch a Lovable MVP in 2026 AI tools can spin up polished apps in a weekend, which makes it easier than ever to build the wrong thing. ·thoughtbot blog ↗
  7. When to build an in-house engineering team and when to hire an agency Our best advice, after thousands of engagements, on when to hire in-house and when to find an external partner. ·thoughtbot blog ↗
  8. Does thoughtbot offer AI-assisted programming? Whether generative AI creates more or less work for developers. ·thoughtbot blog ↗