There’s a pattern emerging, and I get it. Engineers insist AI will never match real architecture or production quality. Designers argue craft can’t survive without clean handoffs and rigid design systems. Product leaders claim strategy and prioritization are immune. I understand the instinct. When your identity is built around a discipline, you protect it. The workflows we’ve organized our careers around are collapsing, and it’s happening faster than we want. If you hang around here, I’m going to say what is changing and posit how to adapt. This is our new reality, we have to get ahead of it.
I’ve spent my career moving between writing code, architecting systems, founding companies, and leading product and engineering teams. I’ve built 0–1 products alone and operated at internet scale. I still ship code. I’m actively building with AI in production. From that vantage point, what’s changing isn’t that humans have stop mattering. It’s that the silos between disciplines are disappearing. Design happens in code. Architecture decisions are shaped by product context in real time. Strategy gets tested instantly. The future belongs to the people who can move across those silos instead of defending them.
The real risk isn’t that AI replaces your job title overnight. It’s that headcount expectations are compressing at every stage. Large companies are seeing the opportunity to optimize revenue per employee. Series A teams that once needed fifty people will run with twenty. Seed teams that once hired across five functions will hire across three. Pre-seed companies that traditionally split engineering, product, design, marketing, and sales across a handful of people will consolidate even further. This is not a temporary efficiency wave. It is a structural shift, and it’s happening faster than we were expecting. The implication is simple: more depth per person, across disciplines. That applies whether you’re at internet scale or building something with five people and a runway.