Taking Back "Software Engineering"
summary
Argues that software becomes real engineering when teams apply iterative, empirical science: five practices—iterative, feedback-driven, incremental, experimental and empirical—drive decisions. Uses Continuous Delivery techniques (automation, test-driven development, hypothesis-driven releases) and NASA case studies: Saturn V modularity, Apollo 13 repurposing the lunar module as a lifeboat, and the Ranger series of experimental missions that fail fast early then yield successes. Claims these concrete practices produce measurable quality and learning.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 2:27Scrum
- 3:55History of Production
- 11:20Engineering in different contexts
- 13:10Engineering definitions
- 14:15Software engineering principles
- 19:32Feedback
- 20:40Incremental
- 25:50Experimentation
- 26:59Alan Shepard
- 28:14Kennedys Vision
- 30:39The EarthMoon System
- 32:54The Ranger Program
- 38:10Empiricalism
- 41:47Continuous Delivery
- 44:00Conclusion
related talks
55mEngineering for Software
41mComputer Science, Software Engineering, and the Scientific Method
01h 01mEngineering for Software - How to Amplify Creativity
42mwhy software development is an engineering discipline
47m‘Engineering' for Software - How to Amplify Creativity
38mSolving the Hard Problems
37mEngineering for Software
27m'The Art of Software Development'
