Technical
The Skill Soup Theory of 2026 Developers
The specialist narrative is wrong for 2026. The most valuable engineers I see are not frontend experts or backend experts. They are generalists with a deep pocket of one specialty. I call it the skill soup: a broad base of competence with one dense ingredient. Here is how I am structuring my own learning this year and how I hire collaborators when I need help.
The Base Layer
Every working engineer in 2026 should be fluent in:
- One typed language (TypeScript or Python with types)
- Git, Docker, and at least one cloud
- HTTP, SQL, and basic auth patterns
- Prompt structuring for model calls
- Basic observability (logs, metrics, traces)
Fluent means you can sit down and work without reaching for documentation on the fundamentals. The base layer is not optional. Without it, the dense ingredient cannot ship because too much time is spent on the surrounding plumbing.
The Dense Ingredient
On top of the base, pick one:
- Distributed systems
- Browser performance
- Embedded and hardware
- AI infrastructure and evals
- Security engineering
- Data engineering and pipeline design
The dense ingredient is what clients buy. The base is what lets you survive without asking for help. Trying to have two dense ingredients at once stretches your attention too thin and you end up shallow in both.
What I Am Adding to My Soup
My dense ingredient for 2026 is evals and observability for agent systems. It is the skill nobody has enough of and every agentic project needs. I am spending two hours a week on it and publishing notes as I learn. The public notes are the accountability layer. Without them, the two hours would quietly disappear into other work.
The Wrong Move
Trying to be deep in three things at once. You cannot. Depth compounds, breadth distributes. Pick one depth and rotate the base layer as needed. Engineers who try to go deep in three areas at once tend to stall at medium in all three.
How to Pick Your Dense Ingredient
Look at the work you already turn down or subcontract. The gap between your current skills and what you could charge for is often the right specialty to grow into. You already have client demand. You just have not caught up to it yet.
RELATED READING
The Consulting Shift I Am Making In Year Two
After a year of writing and building, my consulting practice is changing shape. Shorter engagements. Sharper outcomes.
ReadThe Frontend Shift: Shipping Less JavaScript In Year Two
A year ago I reached for Next.js for everything. This year I often reach for nothing.
ReadThe Serverless Lesson I Would Write On A Sticky Note
After a year of shipping serverless projects, one rule explains most of the wins and all of the losses.
Read