new model for engineering team structure in 2026:
2 people only
one pirate and one architect
the pirate's job is to move as fast as possible to develop valuable, shipped product features by vibe coding.
the architect's job is to turn the product surface discovered by the pirate into a reliable, structured machine—also by vibe coding, but at a slower, more well-reasoned pace.
every product needs a pirate but most product's only need an architect once they some form of PMF, and in that case they usually don't need one full-time. architects can work across many codebases and solve interesting technical challenges. pirates go hard on a product that they own end-to-end.
2 people only
one pirate and one architect
the pirate's job is to move as fast as possible to develop valuable, shipped product features by vibe coding.
the architect's job is to turn the product surface discovered by the pirate into a reliable, structured machine—also by vibe coding, but at a slower, more well-reasoned pace.
every product needs a pirate but most product's only need an architect once they some form of PMF, and in that case they usually don't need one full-time. architects can work across many codebases and solve interesting technical challenges. pirates go hard on a product that they own end-to-end.
if you want to see how we run engineering teams @every, read this: every.to/chain-of-thoug…
• • •
Missing some Tweet in this thread? You can try to
force a refresh
