Software Enginnering: The Genesis

on YouTube ↗14m

" summary

The term originates at the 1968 NATO conference and the original transcript shows concrete claims: design with testing interlaced — essentially test-driven design — iterative stages that produce deployable increments, and the warning that teams larger than 20 tend toward disaster. The waterfall diagram appears but the paper calls it risky; many later fads (microservices, Go’s generics debate, renamed monad transformers) rename old practices without solving the core coordination, naming and deployment problems.

AI-written summary · about

" chapters (17)

1. 0:00Intro
2. 2:41Software Engineering
3. 3:06TestDriven Design
4. 3:58DomainDriven Design
5. 4:51Whiteboard Process
6. 5:23Diagram
7. 6:05Waterfall
8. 7:37Naming things
9. 8:05Microservices
10. 9:06Solar
11. 9:59Problems
12. 10:29Programming languages
13. 10:46Go
14. 11:23What is software engineering
15. 12:07Demand for software engineers
16. 12:36Transformers
17. 13:39Outro

" related talks

• 57mEngineering for SoftwareDave Farley · Agile India 2022
• 45mTaking Back "Software Engineering"Dave Farley · GOTO Oslo 2020
• 01h 01mEngineering for Software - How to Amplify CreativityDave Farley · YOW! Melbourne 2022
• 37mEngineering for SoftwareDave Farley · Craft Conference 2022
• 38mSolving the Hard ProblemsDave Farley · GOTO Copenhagen 2024
• 35mEngineering for Software - How to Amplify CreativityDave Farley · Craft Conference 2023
• 55mEngineering for SoftwareDave Farley · YOW! Melbourne 2022
• 47m‘Engineering' for Software - How to Amplify CreativityDave Farley · GOTO Copenhagen 2021