Explicit scenarios for software-engineering income disruption (5-year, 10-year, worst-case). A skill-as-asset map of your current stack — what commoditizes, what compounds, what's protected by domain or relationship. A barbell positioning of capital and effort. The "income halves for 24 months" stress test, run and documented. Your Personal Operating Model updated with Base / Disruption-Light / Disruption-Hard scenarios. Scenario planning is what every founder does for the company and almost no engineer does for the income that depends on it. The barbell is portfolio-of-bets discipline applied to a career: safe core, asymmetric experiments, no mushy middle. The skill audit is build-vs-buy turned on your own capabilities — some skills are durable assets, some are depreciating opex, and founders distinguish these for products while rarely doing so for themselves. And the disruption pattern, where it comes, will not be a single dramatic event: it will be a slow quarter, then an unrenewed contract, then a six-month gap — each step looking like an ordinary cycle until they accumulate. The plan that survives is the one written in daylight, while the numbers are strong. That is what this module is for.
This course unlocks once you've finished its prerequisite. Open prerequisite →
I want to start with something that should be obvious and apparently isn't, which is that an AI writing a personal-finance module about AI's effect on the reader's income is a gen…
Most personal-finance writing assumes a stable income trajectory: you'll earn what you earn now, plus inflation, until retirement. For software engineers, that assumption is now a…
Approach: Essential
Approach: Essential
Approach: Essential
Approach: Important
Approach: Important
Approach: Important
Approach: Important
1. Build the skill-as-asset map: every skill in your stack classified commoditizing / compounding / domain-protected / relationship-protected, with one sentence of reasoning each.…
10 lessons. Read in order; spiral back when you need to. By the end you'll have used the core ideas twice — once on the abstract, once on something you'll meet at work next week.