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
The Software Estimation Paradox
Codehort and Coaching with Michael Migliacio
Mobbing in Scrum: How could this Possibly be Efficient? with Dan Puckett
Safe Peer Driven Goal Setting with 360 Retro
Remote Mobbing with Strangers with Llewellyn Falco and Jay Bazuzi
Dynamic Remobbing at Scale with Ron Quartel
Matthew Killoran: Spock or Skynet?
Peer Promotion Process
The Business Value of Joy with Rich Sheridan
Mob Programming with Agility (Not Formulas) with Allen Holub and Rob Williams
Adapting to a Global Pandemic with Collaboration, Community, and Joy with Christopher Gallivan and James Simon
Mobbing, Collaboration, and COBOL for Results with Dave Nicolette
PubMob with Jeff Langr
Economies of Swarming & Mobbing with Steve Tendon
mobti.me with Alex Barry
Mobbing, Science, and Education with Nick Del Grosso
Agile Fluency and Ensemble Programming with Diana Larsen
Mobs of Embedded TDD Zombies with James Grenning
n > 2 Programming with J. B. Rainsberger
Introducing Mob Programming with Empathy with Alex Bird
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