why software development is an engineering discipline
summary
Argues that software is engineering by showing what actually works: iterative, empirical development where code-as-document and test-driven validation replace heavyweight paper specifications. Cites concrete contrasts — mathematical models saved cost in aerospace but failed in Tacoma Narrows, physical tests proved Boeing wing models, Gaudí used inverted-string models to validate cathedral vaults — and points to tools people use today (unit tests, RSpec, Cucumber, short releases, pair programming) and the economics that make rapid build-and-test practical and reliable.
AI-written summary · about
chapters (8)
- 0:00Software engineering debate
- 1:51Misconceptions about SE
- 8:15What engineering really is
- 16:42Math vs engineering designs
- 29:07Defining software engineering
- 33:43Economics: SE vs traditional
- 40:54Empirical and rigorous SE
- 41:15Conclusion
related talks
42mwhy software development is an engineering discipline
45mTaking Back "Software Engineering"
55mEngineering for Software
27m'The Art of Software Development'
35mCraft, Engineering, and the Essence of Programming
41mComputer Science, Software Engineering, and the Scientific Method
37mEngineering for Software
01h 01mEngineering for Software - How to Amplify Creativity