tl;dr: Chill, y’all – AI will not devour SE
summary
Claim: AI will not destroy software engineering; software engineering is design‑heavy, context‑rich work that already assimilates AI ideas (linked lists, functional programming, expert systems) and therefore adapts to generative AI and LLM components. Practical details: expect AI as co-pilot suggestions for repetitive code, new probabilistic components that require guardrails, integration work and architecture patterns, and increased need for data curation and testing. Consequence: correctness shifts from formal proofs to layered assurance and supervised use, so software engineering must rethink correctness.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:26SE is alive despite AI fears
- 3:56Defining SE and distinctions
- 6:43Programming abstractions evolution
- 9:56SE’s social context
- 12:26SE’s history with AI
- 15:32AI’s statistical vs formal nature
- 19:43AI contribution to SE practices
- 23:38AI-integrated architectures
- 26:49AI impact on jobs and productivity
- 30:22AI risks and oversight need
- 33:35Rethinking correctness in SE
- 37:07AI correctness challenges
- 39:55Three key takeaways
- 40:58Q&A: Legal responsibility
- 43:27Q&A: Flexibility with AI
- 45:35Q&A: Exploratory programming
- 47:42Q&A: Reliability with AI
related talks
09mLessons Learned in AI Engineering
27mThe new gravity of software engineering in the AI-first era
24mThe Impact of AI on the future of software engineering
56mFundamentals of Software Engineering In the age of AI
07mAI's impact on programming jobs and developer skills
37mHow AI & automation are changing software engineering
27mEngineering in the Age of AI: Making AI Work for Us, Not Replace Us
25mThe role of software design in an AI world