Generalist vs Specialist
For a founding builder, range beats narrow depth. The generalist who sees the whole system makes coherent decisions a specialist cannot.
The Thesis
Kevin's bet is on range, made deliberately and with eyes open about the cost. Forward Deployed describes the ten-hat model: infrastructure, backend, auth, frontend, billing, devrel, design, security, ops, and culture, with three to four context switches a day. The cost is depth, you can never go as deep on any single surface as a specialist would. The advantage is coherence, you see the entire system at once so decisions stay consistent and the architecture does not fracture along team boundaries. Source: Forward Deployed, 2026-05-08
Depth Debt Is a Choice, Not a Failure
The generalist accepts depth debt on purpose. The billing system might be eighty percent as resilient, the design eighty percent as polished, but the product ships and the pieces cohere. Source: Forward Deployed, 2026-05-08 The unfair advantage is the cross-links: when you fix a billing bug you already know how the webhook hits the API because you wrote the API. The hats are not independent, they are wired together, and the wiring is the edge.
Range Beyond Code
What Is Engineering supports the stance: engineering is holistic product creation, not applied science. The scope is the product, not the problem set, which is inherently a generalist's scope. Source: What Is Engineering, 2026-05-17 Career Profile frames Kevin's differentiator as taste and range, spanning design systems, motion, 3D, a hand-rolled game engine, breakdancing, and powerlifting, not a generic single-lane SWE profile. Source: Career Profile
When the Specialist Wins
This is not a claim that breadth always beats depth. The generalist wins at the founding-team scale, where surface area is enormous and there is nobody else to own a hat. As organizations grow, specialists go deeper than any generalist can, and the generalist's job shifts to wiring their depth together. The skill is knowing which regime you are in.
Connections
| Connection | Implication |
|---|---|
| Learning by Shipping | Range is accumulated by shipping across domains, not by formal study in each. |
| Taste as a Moat | Range plus taste is what lets one person keep a whole product coherent. |
| Ownership & Agency | At founding scale, ownership spans domains you did not pick, which forces the generalist mode. |
Anti-Patterns
- Pretending to be a specialist in all ten hats instead of owning the coherence between them.
- Refusing breadth out of fear of being "not technical enough" in any one lane.
- Forcing the generalist mode at a scale where specialists would clearly go deeper and better.
Timeline
- 2026-05-31 | Compiled from Forward Deployed (ten hats, depth debt, cross-links as advantage), What Is Engineering (engineering is holistic, product-scoped), and Career Profile (taste and range as differentiator). Source: compiled from wiki graph