You've added the retros. The sprint gates. The review cycles. And somewhere along the way, your team stopped shipping and started managing the process you built to help them ship.

Patrick Byrne, VP of Engineering at Dribbble, has spent over a decade running a top-1,000 site on a majestic Rails monolith with a lean team of six. He's lived every one of those cycles of process expansion and contraction too.

Here's what he figured out:

• Process creep is invisible until it isn't. Build teams safe enough to say so before it's too late.
• Green builds can't catch what you didn't think to test. Ship small, monitor hard, recover fast.
• The code you're proudest of is probably what your team dreads touching. Boring code is a production virtue, not a compromise.

Highlights:

(00:00) Intro & Dribbble overview

(02:14) Engineering team size & the Rails monolith

(03:27) From sprints to continuous delivery

(06:39) Stripping back process without losing rigor

(10:14) QA, edge cases & the limits of testing

(11:18) Error tracking with Honeybadger

(13:22) Accepting bugs as inevitable

(14:30) Getting engineers into product decisions earlier

(17:05) From clever code to boring code

(22:55) Balancing coding and people management

(26:30) Hiring for ownership

(30:50) "Tell me when you took down production"

(33:25) Dribbble's pivot to marketplace

(35:55) Platform health & containerization

(40:27) Where to find Patrick

Connect with Patrick on LinkedIn
Connect with Chris on LinkedIn