Your job was never to write software.

Matt Brown, CTO at Opendate, has spent his career moving between 50-person startups and orgs the size of Salesforce, and what he's learned is that engineering value has always lived somewhere other than the code itself. AI just made that impossible to ignore.

In this episode, Matt and Chris get into how influence and political capital work in inverse proportion to headcount, why constraints make engineers better rather than more limited, and what the job actually becomes once the machine is writing the code.

Highlights

(00:00) AI opinions change every two weeks
(01:06) Matt Brown's career: 50-person startup to Salesforce
(03:52) Why influence shrinks as org size grows
(09:28) The real cost of AI tooling
(12:09) How business model shapes engineering decisions
(15:31) Context vs. constraints: humans vs. AI
(17:32) Nice to have is a must-have
(26:33) Your job was never to write software
(28:56) The junior engineer pipeline problem
(33:39) Shifting quality left
(34:41) The future of engineering jobs isn't shrinking, it's changing

Connect with Matt Brown on LinkedIn
Connect with Chris on LinkedIn

Check out Axiomatic on LinkedIn

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

Software engineering is getting weirder by the week. AI is reshaping how teams work, org structures are straining under the pressure, and the old playbooks don't quite fit anymore.

The Hallway Track is a podcast for engineering leaders who are in the middle of all of it - CTOs, VPs, and managers at real companies, figuring it out in real time.

Every other week, I’ll be sitting down with the people actually doing the work: engineering leaders navigating acquisitions, rebuilding broken processes, connecting their teams to the business, and experimenting their way forward, without copying what some FAANG company did five years ago.

No keynote wisdom or recycled frameworks. Just honest conversations about what's changing, what's breaking, and what's actually working today.

Because the best lessons in software engineering don't happen on a stage. They happen in the hallway.