How we changed our world
summary
Developer community claims concrete wins: unit testing (JUnit in 1997) cuts late bugs, the Agile manifesto (2001) shifts feedback into short cycles, DevOps (~2009) creates automated pipelines and monitoring, and Domain-Driven Design since 2004 forces models in domain language. Practical tools used include event storming and domain storytelling; teams run a design studio with paper mock-ups built in the next iteration and approved by users. Example failures include hospital software that removed a useful physical cue, and the company reports 120 people with 25% female developers. Continuous improvement shows a dip before real gain.
AI-written summary · about
chapters (6)
- 0:00Start
- 2:57Sustainable Software Architecture
- 15:18The Agile Manifesto
- 20:22Scrum
- 21:35Why Did We Need Help
- 23:41Domain Storytelling
related talks
01h 22mAgile - The Road Towards Organizational Agility - Progress & Challenges Examined
58mDeveloper Joy – How great teams get s%*t done
45mHalf a Century Fighting Legacy
22mA Healthier Software Development Life Cycle with DevOps
32mTales from the DevOps Transformation Trenches
54mGetting Unstuck. Strategies for Surviving in a Rapidly Changing Post-Agile World
35mSoftware Engineering - Development in 100 Years Time
50mTactics and strategies on software development: how to reach ...