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
Q & A on High Quality, High Release Frequency, and High Psychological Safety
Dojos and Coaching for Learning Beyond Facilitation with Joel Tosi and Dion Stewart
Overcoming the Groan Zone, Bad Habits, and Entropy with Mark Pearl
Reflection & Refactoring Rhythm with Giorgio Sironi and Kevin Rutherford
Stop Suffering with Training: Use Learning Ensembles with Ted M. Young
Task Force Driven Development with Steve Bishop
Clear & Simple with Dustin Thostenson
What Goes on in Dedicated Learning Time?
Collective Product Ownership
The Joy of Continuous Delivery with Dave Farley
Throughput Accounting for Knowledge Work with Daniel Doiron
Creating Coding Careers via Mob Programming with Mike Roberts
Mob Programming from a College Student’s Perspective with Jack Wei, Joel Plotnik, and Alec Arce
Mob Emails and Communication
Refactor, THEN... Red Green Refactor
Ludicrous Speed Learning with Willem Larsen
Rethinking Management and Nurturing Change with Esther Derby
Mobbing in the Early 2000s with Moses Hohman and Andy Slocum
High Octane vs. Zen Mob Programming
Mobbing with Finance
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