One Builder, Many Futures

The talk opens with a question: what if "pick a lane" is the wrong career advice for the world we're actually shaping? The old playbook was to choose one specialty, go deep for forty years and become "the X person". That worked when industries stood still. Today AI collapses the cost of learning a new domain, the speed of change beats depth in a single static lane, and the best opportunities sit between fields rather than inside one.

The case rests on one builder's path across four industries: SaaS products for other founders, payment and booking platforms in fintech, token-based engagement platforms in Web3, and algorithmic trading systems. The problems differ, but the engineering brain is the same. Learning to code, to trade and to ship products turn out to be one skill all along: pattern transfer. Range compounds faster than depth alone.

The framework is Anchor, Rotate, Ship. Pick one core skill as the engine (engineering, design or writing), point it at a new domain every 6 to 12 months, and build in public so each domain becomes portfolio rather than a detour. The obvious objection is that this makes someone a jack of all trades. It only does if the skill is rotated. Rotate the domain instead and the anchor keeps getting deeper: depth in the engine, range in where it is pointed.

The talk closes by shifting the question from "What do I want to be?" to "What can I build next, and what will it teach me?", with a challenge for the quarter: pick an anchor skill, pick one domain outside the comfort zone, and ship something small in it before the quarter ends.