00:00+5
Act 1
It worked once
Open with a persuasive artifact and question what that proves.
Alternative trajectory
From Plausible Output to Dependable Systems
“The demo worked. Do we have a result—or do we have a working system?”
A prompt can produce an outcome; software makes it observable, repeatable, governable, and scalable.
Thesis
The enduring engineering opportunity is not privileged knowledge of syntax, but the ability to turn powerful, unreliable components into systems that deserve bounded trust.
45:00Run of show
The narrative, minute by minute.
The intellectually crisp, engineer-centered version with the strongest technical explanation.
05:00+6
Act 2
Crossing boundaries
Use personal examples to establish what cheap implementation makes possible.
11:00+8
Act 3
The system around the model
Decompose model, context, instructions, tools, orchestration, and evaluation.
19:00+7
Act 4
Failures have addresses
Replace the word hallucination with a small, actionable failure map.
26:00+7
Act 5
Two kinds of correctness
Distinguish a valuable outcome from a system that can produce it dependably.
33:00+8
Act 6
Feedback connected to reality
Demonstrate tests, Git, previews, evidence, and milestone review.
41:00+4
Act 7
The converging role
Close on the path from intention to consequence and why no profession owns it automatically.
It gives a precise, practical answer to why software engineering still matters.
It can become a technical AI architecture lecture with the career, community, and identity arguments attached afterward.
Impressive result → suspicion → decomposition → earned confidence
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
- System around the model
- Failure taxonomy
- Outcome vs system correctness
- Feedback
- Professional convergence
Park with confidence
- Extended emotional cost
- Lost mastery
- Communities of practice
- Engineer archetypes
- Accountability-sink politics
Go to the thinking