Half a Century Fighting Legacy
summary
A historical survey from the 1960s to the mid-2010s examining modern software-development misconceptions. It analyzes why practices like Git-flow, feature branches and pull requests are criticized; argues manual testing is problematic and automated tests are developers’ responsibility; and considers how DevOps became a separate profession and how Scrum can work (or not) without strict ceremonies, emphasizing the need for solid technical practices.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:05Fighting conventions
- 8:37Legacy code problem
- 13:12Why waterfall fails
- 17:05XP and refactoring
- 23:03CI and merge conflicts
- 27:43XP practices together
- 31:14Continuous Delivery and infra
- 36:38Results of practices
- 41:44Q&A
related talks
39mHow we changed our world
49mExtreme Professionalism - Software Craftsmanship.
39mRethinking the SDLC
50mTactics and strategies on software development: how to reach ...
35mSoftware Engineering - Development in 100 Years Time
57mStop writing software like it's 1999!
54mGetting Unstuck. Strategies for Surviving in a Rapidly Changing Post-Agile World
22mShifting Left, Shifting Right