Every company is building agents. The harder problem is the layer above them: the system that coordinates those agents against the actual shape of the business.
Two months into building AI-first at Imprint, here's what I'm learning about the systems👇
https://t.co/ASFWOqjQCZ
It's: how do we detect when they start drifting in a system that is 100x smarter than us?
The technical alignment problem and the organizational alignment problem might be more connected than we think.
Something I can't stop thinking about after reading @DarioAmodei's essays:
We talk a lot about giving AI the right principles. But in my experience scaling orgs from 1,500 to 15,000 people, the most dangerous moment is when the RIGHT principles become the WRONG ones.
I've seen organizations with the right principles grow and fail to adapt to that growth. Those "right principles" turned into poison and became the forcing function of downward spirals into deeply toxic cultures.
So the real question isn't: did we get the principles right?
The part that everyone knows: A players hire A players. B players hire C players.
The part that isn’t called out enough: B players will suffocate A players.
@JetBlue Your agent confirmed my family could move together, so we agreed. Mid-change they said we couldn’t — and our original seats were lost. Now 1 person’s moved, 2 aren’t. This was your system’s error. Please fix so our family can fly together tomorrow.
@JetBlue This is unacceptable. Your agent confirmed that my family could be moved together, so we agreed. Then mid-change, they said we couldn’t, and our original seats were lost. One was moved, two weren’t. This was your system’s error. We need our family rebooked together.
A Stanford Sophomore floored me with this comment today:
It's easier as a Stanford student to get into YC than get an internship at a reputable company. Everyone knows this and every batch there're Stanford founders who did it because they had no other options.
Vibe coding works—until it doesn’t. And by the time it doesn’t, you’re already in technical debt.
Leadership means knowing when to trade speed for structure—before the system forces your hand.
Structure isn’t bureaucracy. It’s care.
And care scales.
🧵End.
🧵 Where “vibe coding” breaks down—and what strong engineering leadership does instead.
It’s easy to “just ship it” in the early days. But as your system grows, so does the cost of casual decisions.
Here are 3 places where good vibes aren’t enough—and what to do differently: