become a generalist.
specialization makes you efficient. generalization makes you dangerous.
what it actually means:
• learn across domains → math, physics, software, economics, biology. patterns repeat across fields.
• connect ideas → innovation happens at the intersection, not inside silos.
• adapt fast → when one field shifts, you don’t collapse, you pivot.
• see systems → specialists see parts, generalists see the whole
• build end-to-end → from idea → design → implementation → delivery
the world rewards specialists in stable environments.
it rewards generalists when things are changing.
right now, everything is changing.
don’t just go deep.
go wide, then stack depth where it matters.
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.
AI pricing models are interesting. I think there is going to be some extreme margin opportunities here because what they are replacing can be very costly.