The Future of Software Engineering
summary
Argues that scale is an architecture problem, not a process one, and shows concrete pivots: Google File System + MapReduce inspired Hadoop for horizontal data processing; Amazon splits transactions into services with eventual consistency and teams owning data, spawning EC2 (Aug 2006) and an $80B run rate; 2012 ImageNet leap (16.4% error) triggers neural stacks like TensorFlow; SpaceX cuts launch cost from $18,500/kg to $2,720/kg by fast fail integrated events; advocates continuous delivery, mission-command briefings and sync‑and‑stabilize rehearsals.
AI-written summary · about
chapters (8)
- 0:00Introduction by host
- 1:27Evolution from past to future
- 19:34Smart technology breakthroughs
- 27:45New technology stack explained
- 28:29Engineering culture and flow
- 33:52Knowledge sharing and military model
- 39:32Future of software engineering summary
- 40:37Q&A session begins
related talks
30mArchitecture & Teams at Less-than-Google Scale
28mSoftware Engineering - Development in 100 Years Time
49mSoftware Architecture, Team Topologies & Complexity Science
30mMoving Fast At Scale
26mScaling engineering organizations
01h 01mSoftware Architecture, Team Topologies & Complexity Science
46mGo Faster -Impact on Technology, Process and Organization
56mScaling Up!