00:00+5
Act 1
What is actually dying?
Separate the profession from its old unit of scarcity.
Alternative trajectory
Rebuilding Professional Identity
“The reports of our death may be exaggerated. The end of our old identity may not be.”
If writing code becomes less scarce, what should a software engineer understand their value to be?
Thesis
Software engineers have a favorable starting position—not a protected destination—and must expand from making toward directing, deciding, connecting, and owning outcomes.
45:00Run of show
The narrative, minute by minute.
The most personal, future-of-work, and broadly accessible trajectory.
05:00+10
Act 2
My trajectory
Move from neuroscience through software and infrastructure into AI-assisted full-stack product work.
15:00+7
Act 3
What expansion costs
Name lost mastery, shortened comprehension, and cognitive saturation.
22:00+7
Act 4
Four dispositions
Replace job-title competition with making, directing, deciding, and connecting.
29:00+7
Act 5
A converging role
Bring outcome and systems correctness together from intention to consequence.
36:00+5
Act 6
One real workflow
Demonstrate milestones and feedback as evidence rather than a tool tour.
41:00+4
Act 7
Reinvention without prediction
Close on staying in the loop as a career stance rather than occupational reassurance.
It makes the title do real work and gives the audience permission to grieve the old craft while choosing a new identity.
Without a tightly integrated demonstration and specific examples, it can drift into generic future-of-work speculation.
Loss → inventory → possibility → deliberate reinvention
Promises covered
- 1Personal journey✓
- 2Expanded capability & its costs✓
- 3Why engineers may be prepared✓
- 4A hands-on account of changed coding✓
- 5Human collaboration & community—
- 6Judgment, responsibility & purpose✓
Foreground
- Career story
- Lost mastery
- Four dispositions
- Outcome and system correctness
- Deliberate reinvention
Park with confidence
- Failure taxonomy
- Detailed milestone mechanics
- Vendor architecture
- Most organizational speculation
- Parallel work details
Go to the thinking