Software Engineering - Development in 100 Years Time
summary
Predicts programming languages and paradigms deliver no order‑of‑magnitude gains; a small CRUD experiment shows Angular produces roughly 4× the code of a mid‑90s JS/Java/HTML/CSS version. Argues frameworks often increase accidental complexity, and service boundaries plus stateful serverless need better language/runtime support. Claims test‑driven design (not just testing) removes ~70% of common production failures and expects kindergarteners to learn it in 100 years. Champions Continuous Delivery as an engineering foundation that enforces iteration and feedback and modularity and separation of concerns.
AI-written summary · about
chapters (20)
- 0:00Intro
- 1:48Software development 100 years ago
- 4:15Big assumption
- 5:03Idea: Language
- 8:30Prediction
- 9:18Idea: Frameworks
- 12:10Prediction
- 13:17Idea: Programing paradigm
- 15:52(Risky) Prediction
- 19:49Idea: TDD
- 20:50Prediction
- 23:33Ideas: Iteration, feedback, incremental, experimental, empirical
- 25:31Prediction
- 26:29Observation
- 28:34Ideas: Modularity, separation of concerns, info hiding, loose-coupling, cohesion
- 31:00Prediction
- 31:33Observation
- 32:49Idea: Continuous delivery
- 34:37Prediction
- 34:54Outro
