The Gap Is Not Coding Anymore
AI is changing the old equation — domain experts can prototype without a dev team first. The scarce gap is no longer can you code; it is whether you understand the problem deeply enough to evaluate what gets built.
That is loosening. Domain experts can build prototypes themselves — scripts, internal tools, first-pass products — faster than a hiring cycle.
The challenge is not writing code anymore. It is learning enough engineering discipline to evaluate, test, and evolve what gets built.
Two kinds of depth
The gap I see is not between people who can code and people who cannot.
It is between people who understand the problem deeply and people who understand the implementation deeply.
The most interesting builders lately are learning just enough of the other side to close that gap.
In regulated domains — healthcare, life sciences, fintech-adjacent work — domain expertise is often far rarer than another software engineering degree. The person who has lived the workflow usually sees the failure modes first. AI lowers the cost of turning that sight into something testable.
That does not replace engineers for production systems. It changes who gets to falsify ideas before capital and calendar time are committed.
What AI does not remove
Lowering the cost of execution does not lower the cost of:
- Knowing what to subtract
- Designing for rollback and audit
- Holding context across handoffs
- Making something survive Monday morning traffic
Those are operational problems. They are why we argue operations was always the strategy — and why memory infrastructure matters once prototypes graduate (capture once in production).
A reply worth making in public
When someone asks whether they should learn to code or find a technical cofounder, the honest answer in 2026 is often a third path:
Build the smallest test that proves you understand the problem. Learn enough implementation literacy to know when the test lies. Then decide if you need a team.
AI is not replacing expertise. It is lowering the cost of execution for people who already understand the system.
If that is your path — operator, domain expert, reluctant founder — About is written for you. If you are past prototype and need production rails, Signal with what you have and what broke.