How do you end up with legacy code? How come things don't go as planned? Is it as simple as one bad process/practice? Bad tech? Bad people?
Conway’s Law describes how team structure influences software structure. But, does software structure also influence team structure? Is there a bidirectional feedback loop between people and code?
Join Chris and Austin as they discuss with Michael Feathers about how we can learn to better see our sociotechnical systems and factor that into our decision-making. In addition we talk about the dynamics of team/org sizing and specialization. Lastly we talk about the impact of Mob Programming on a system and the role of an architect.
Video and show notes: https://youtu.be/AC4ZvN6riPE
A Quest for Value with Colleen Kirtland
Live Mob Programming at Agile Open SoCal
Dynamic Reteaming with Heidi Helfand
Freestyle Mob Programming with Jen Diamond
Mob Programming and Fear with Thomas Cagley
Agile Planning for Mob Programming
Making Training Stick with Camille Bell
Remote vs. In-Person Mob Programming with Sandra Spaeth
Team Decision Making
Agile vs. Agility with Allen Holub
Ensemble Testing with Lisa Crispin
Second Order Effects
Mob Programming Domain Driven Design with Julie Lerman
Mob Programming at Scale with Andy Graham and Sean Cowan
"My Turn is for Learning" Mob Programming Pattern
MobRetreat with Bob Allen and Dimitry Polivaev
Team Oriented Development with Florian Schneider and John Fletcher
Mob Programming at a Startup with Mike LaRocca
How Do Bad Practices Leave the System?
Mob Programming Embedded Systems with David Bishop
Create your
podcast in
minutes
It is Free
Insight Story: Tech Trends Unpacked
Zero-Shot
Fast Forward by Tomorrow Unlocked: Tech past, tech future
The Unbelivable Truth - Series 1 - 26 including specials and pilot
Lex Fridman Podcast