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
Mob Programming Roles: Major Pain and Dr. Feel Good
Socratic Learning and Tech Optimized Interpersonal Interactions with Michael Strong
Legacy Code Refactoring and Mending with M. Scott Ford
Models of Teaching and Learning in Mob Programming
AI Enabled Mobs for Learning with Carolyn Rosé
The Samman Technical Coaching Method with Emily Bache
Mob Programming Interviews
Mobbing with UX Designers with Gary Saunders
Finding Mutual Understanding with Jenny Carlston
Are Async Code Reviews Killing Your Company’s Throughput? with Dragan Stepanovic
Modern Management with Johanna Rothman
The Zen of Remote Mob Programming with Elena Rosheva and David Legge
Collaborative CompSci Coding for K-12 with Jeanine Rioux and David Coopersmith
Better Thinking and Change Initiatives with Linda Rising
Fail Fast, Correct Fast: Communication Flow with Mark Holmes
Onboarding Jr. Devs via Mob Programming with Ben Holmes
Ship of Theseus Analogy for Teams
Forming Cohesive Teams with Jacques Blom, David Chaplin, and Dean Gracey
Put PEPPER on your Agile Before You Eat It with Kyle Griffin
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