Mob Programming Meets Neuroscience: Exploring Brainwaves and Team Dynamics with Mike Bowler

The Mob Mentality Show

Player FM - Internet Radio Done Right

12 subscribers

Đã thêm cách đây năm

Nội dung được cung cấp bởi The Mob Mentality Show. Tất cả nội dung podcast bao gồm các tập, đồ họa và mô tả podcast đều được The Mob Mentality Show hoặc đối tác nền tảng podcast của họ tải lên và cung cấp trực tiếp. Nếu bạn cho rằng ai đó đang sử dụng tác phẩm có bản quyền của bạn mà không có sự cho phép của bạn, bạn có thể làm theo quy trình được nêu ở đây https://vi.player.fm/legal.

Species Unite

1
Andrew Stein: Living with Lions 46:39

cách đây 11 ngày trước46:39

Nghe Sau

Danh sách

Thích

Đã thích

46:39

“If we march into that village and we start trying to persecute people for using poison, something that's very illegal, nobody's going to talk to us. We're not going to find out where the poison came from. We're not going to be able to shut anything down. We should take the approach that people are using poison because they're desperate, because they see no other alternative.” – Andrew Stein Andrew Stein is a wildlife ecologist who spent the past 25 years studying human carnivore conflict from African wild dogs and lions in Kenya and Botswana to leopards and hyenas in Namibia. His work has long focused on finding ways for people and predators to coexist. He is the founder of CLAWS , an organization based in Botswana that's working at the intersection of cutting-edge wildlife research and community driven conservation. Since its start in 2014 and official launch as an NGO in 2020, CLAWS has been pioneering science-based, tech-forward strategies to reduce conflict between people and carnivores. By collaborating closely with local communities, especially traditional cattle herders, CLAWS supports both species conservation and rural livelihoods—making coexistence not just possible, but sustainable.…

cách đây khoảng một năm trước 49:15

MP3•Trang chủ episode

Join us in this exciting episode of the Mob Mentality Show as we dive deep into the fascinating intersection of mob programming, neuroscience, and team dynamics with the insightful Mike Bowler! Mike brings over a decade of experience facilitating mob programming sessions across hundreds of teams and countless experiments. Whether you're a software developer, team coach, or collaboration enthusiast, this conversation will leave you with actionable insights and inspiring takeaways.
🔍 What We Discuss:
- A Different Approach to Facilitating Mob Programming Sessions
- The Neuroscience of Psychological Safety and Mobbing
- Team Flow States and Brainwave Activity
- About Mike Bowler
📢 Don’t Miss Out!
Subscribe to the Mob Mentality Show on your favorite platform to learn more about innovative collaboration techniques and team success.

🔗 Find us here: https://www.mobmentalityshow.com

Video and show notes: https://youtu.be/okeAxvRggVc

122 tập

#Tech #Business #Mob Mentality

The Mob Mentality Show

Mob Programming Meets Neuroscience: Exploring Brainwaves and Team Dynamics with Mike Bowler

The Mob Mentality Show

12 subscribers

published cách đây khoảng một năm trước

Chia sẻ

MP3•Trang chủ episode

🔗 Find us here: https://www.mobmentalityshow.com

Video and show notes: https://youtu.be/okeAxvRggVc

122 tập

#Tech #Business #Mob Mentality

Tất cả các tập

The Mob Mentality Show

1
No Branches?! Ron Cohen Breaks Down Trunk Based Development and Feature Flags (For Real) 43:48

cách đây 7 ngày trước43:48

43:48

What if your team didn’t need branches at all? 💥 In this episode of The Mob Mentality Show , we sit down with Ron Cohen, CTO and co-founder of Bucket, to unpack the real story behind Trunk Based Development (TBD) and the practical use of Feature Flags. Ron stirred the pot online by challenging common assumptions around TBD — and now he’s here to clear the air. We talk about: What Trunk Based Development really means (Hint: It’s not just “no branches”) Why TBD isn’t just a Git strategy, but a safety mindset often backed by solid practices like Pair Programming, Mob Programming, and TDD (Test-Driven Development) Gitflow vs. TBD — which one sets your team up to move faster and safer? The myth that TBD = chaos, and why short-lived branches might still play a role How mobbing and pairing can make TBD not just possible, but powerful We also dive deep into Feature Flags (a.k.a. Feature Toggles ): Why Ron became obsessed with them — and how they changed how his teams ship code How to use toggles for faster releases, safer experiments, and smoother collaboration between devs, Product Owners (POs), and marketing The difference between feature flags that require a deployment and those that don’t The value of “dogfooding” your features in production before a full rollout Why not all toggles are created equal — from simple UI switches to ops-level controls How to avoid the mess of long-lived toggles and clean up after experiments (Austin, we're looking at you 😅) Plus: How flags can power A/B testing and internal beta programs Fowler’s definition of Feature Flags — and how it is in action Using toggles to build internal and external trust Ron’s framework for different kinds of flags in different contexts Whether you're deep into CI/CD (Continuous Integration/Continuous Delivery), trying to tame your branching strategy, or just want to ship smarter — this episode’s packed with insights you can use immediately. 🎧 Subscribe and listen on your favorite platform: 👉 https://www.mobmentalityshow.com/ Video and Show Notes: https://youtu.be/4PZN1yO8l2c…

The Mob Mentality Show

1
How Software Prof Ben Kovitz Turned His Class into a Live Coding Mob 45:40

cách đây 20 ngày trước45:40

45:40

What happens when a college software design course ditches traditional lectures and embraces Mob Programming? In this episode of the Mob Mentality Show, we sit down with Ben Kovitz, a former software developer turned professor at Cal Poly Humboldt, to explore his innovative approach to teaching software design through mobbing. Topics Covered: ✅ From Industry to Academia: Why Ben left software development to become a professor and how he discovered mob programming. ✅ Redefining Software Education: Instead of 30 traditional lectures on software design, Ben’s students learn by doing—designing software while coding. ✅ The Power of Mobbing in the Classroom: How students collaborate in the mob of 8, rapidly sharing knowledge and tackling challenges together. ✅ Fast Learning vs. Lectures: Why mobbing enables faster knowledge transfer compared to passive lectures. ✅ Strong-Style Navigation: How rotations and fast timers helped to stimulate a highly effective learning environment. ✅ The Role of the Navigator: How students help each other navigate, learn C++ and the QT framework, and document key lessons from each mob session. ✅ Real-World Software Challenges: Simulating legacy code maintenance, evolutionary design, and design patterns like MVC (Model-View-Controller). ✅ Overcoming Student Struggles: What happens when students don’t know how to navigate? How asking for help and learning together fosters growth. ✅ Teaching Through Experience: Letting students experiment with flawed solutions before introducing better design principles. ✅ Assessment & Engagement: How Ben measures student participation, engagement, and learning outcomes in a mobbing environment. Why This Matters: Traditional software design education can leave students unprepared for the realities of refactoring real code and collaborative development. By integrating Mob Programming, refactoring techniques, and hands-on problem-solving, Ben Kovitz is equipping the next generation of developers with practical, real-world skills and deeper design insights. 📢 Subscribe to the Mob Mentality Show to stay updated on the latest insights in Mob Programming, Extreme Programming (XP), Agile, and collaborative software development! 🎧 Listen on your favorite podcast platform: https://www.mobmentalityshow.com 🔔 Don’t forget to LIKE, COMMENT, and SUBSCRIBE for more episodes on software development, coding education, and team collaboration! Video and Show Notes: https://youtu.be/Rajvp2nrg1A…

The Mob Mentality Show

1
Garrick West on 'Building' Great Developers with XP & Agile plus the Best Debugging 48:03

cách đây 28 ngày trước48:03

48:03

🔥 How do you actually build great software developers? How do you debug like a pro? And what happens when XP (Extreme Programming) makes a comeback after the Scrum backlash? Join us as Garrick West—a seasoned XP practitioner, Agile coach, and software craftsmanship advocate—dives into: ✅ Building Agile Software Developers: From XP mentorship to industry-academia collaboration ✅ The Best Debugging Strategies: Unpacking The Debugging Book and applying its rules in a mob ✅ Reviving XP & Software Crafting: Why XP is more crucial than ever in Agile teams 🚀 Garrick's Story: From Early Coding to XP Champion Garrick started coding at 10 years old (at day camps in the 80s! 😅), earned a Computer Science degree, and had his development worldview shaped by reading the first edition of Extreme Programming Explained . He has worked at XP-centric organizations, trained teams in TDD (Test-Driven Development), Ensemble Programming, and CI/CD (Continuous Integration/Continuous Deployment), and even revamped a college curriculum from Waterfall to XP/Scrum. 🎯 "Building" Agile Software Developers The power of an XP coach early in a developer’s journey Public speaking as a dev skill? (Toastmasters, teaching at community college) What happened when Garrick helped convert a college curriculum from Waterfall to XP/Scrum? Industry experts + academia: How can professional devs and educators collaborate better? The apprentice model: What it means and why learning stages (like the Dreyfus Model) matter AI & developer education: Does AI replace early learning stages, or is it just a slick salesman? Scaling Gilded Rose Kata to different skill levels Test Coverage as a red herring—what should we focus on instead? 🐞 Debugging: The Missing Developer Superpower Ever heard of The Debugging Book ? Most developers haven’t—but it’s a game-changer. We explore: Debugging as problem-solving, not just "stepping through" in an IDE The 9 Debugging Rules: From reading the manual to never throwing away a good test tool How to gamify debugging in a mob & introduce a "debugging auditor" role The anti-pattern of multiple experiments at once—and how to avoid it Why debugging is like navigating a labyrinth with a million wrong paths 🔄 Reviving XP & Software Crafting After the Scrum Backlash XP fills Scrum’s missing middle: Building the right thing (Scrum) AND building it right (XP) How Scrum without XP leads to a “Ball of Mud” in just 18 months Why XP + Lean is the ultimate combination Breaking free from sprints & pressure cookers—just focus on continuous iterations Can XP stand without Scrum? Or does Scrum need XP? 💡 Don’t miss this high-energy, insight-packed conversation with Garrick West! 📢 Comment below: What’s YOUR experience with XP, Agile, or debugging challenges? Video and Show Notes: https://youtu.be/vxLDm-13Ny4…

The Mob Mentality Show

1
Game Jams & Mobbing: Supercharging Learning, Speed, and Creativity with James Herr 46:04

cách đây 5 weeks trước46:04

46:04

🚀 How do Game Jams accelerate learning? Can mobbing make game development more effective? In this episode of the Mob Mentality Show, we dive deep into Game Jams, Mobbing, and Game Dev Collaboration with James Herr—a full-stack developer, game dev enthusiast, and published game creator on Steam. 🎮 What You'll Learn in This Episode: 🔹 What Are Game Jams and why they’re a must-try for devs? 🔹 The tech stacks and tools commonly used in Game Jams 🔹 How themes shape a Game Jam’s creativity and constraints 🔹 How James is bringing mobbing into Game Jams 🔹 The difference between solo development, swarming, and full mobbing? 🔹 Pros & Cons of Mobbing Game Jams—Does it boost creativity or slow things down? 🔹 How Discord & Twitch fuel real-time game dev collaboration 🔹 Can Twitch chat act as a “navigator” in game development? Does the live audience guide decisions? 🔹 How Game Jams reveal code smells faster and teach refactoring & design patterns 🔹 Why public game dev can be a game-changer for learning speed 🔹 How Game Jams can simulate real-world software challenges and improve teamwork 🔹 Mob timer tools & Git handover techniques for smoother collaboration 🤝 Why This Episode Matters: Mobbing isn’t just for software teams—it’s transforming game development, learning, and onboarding. James shares his firsthand experience mobbing with kids, running Game Jams with cross-discipline teams, and teaching mobbing roles in game dev. Whether you’re a seasoned developer, indie game creator, or just curious about Game Jams, this episode is packed with actionable insights! 📢 Want to Join the Game Dev Community? James discusses how Discord and Twitch connect developers worldwide, making it easy to collaborate, get feedback, and learn from others. Checkout James' communities here: https://jamcraft.io/ 🎧 Subscribe & Listen Now! Don’t miss out! Subscribe to the Mob Mentality Show and get notified when this episode drops: 🔗 https://www.mobmentalityshow.com/ Video and Show Notes: https://youtu.be/AZEH_FmBBKs…

The Mob Mentality Show

1
TDD, Misconceptions, and Better Testing with Jason Swett 44:51

cách đây 6 weeks trước44:51

44:51

🚀 Why is there so much confusion around Test-Driven Development (TDD) and Automated Testing? Why do many developers struggle with testing, and what are they getting wrong? In this episode of the Mob Mentality Show, we sit down with Jason Swett—author, speaker, and a go-to expert on Rails testing—to unpack the most common misconceptions, challenges, and best practices in modern software testing. 🔍 Topics We Cover: ✅ Why Jason Swett is passionate about Automated Testing and why he wants to help the development community ✅ Misconceptions about TDD (Test-Driven Development)—not liking TDD itself vs. not liking something called "TDD" ✅ The reality of software testing—why most developers aren't doing it well and how to improve ✅ Testing vs. verification vs. specification—what is a test really? What is code? ✅ Red, Green, Refactor vs. Specify, Encode, Fulfill—what do these different ways of thinking about TDD highlight? ✅ Why software changeability matters and how to reduce the cost of ownership ✅ What are you actually testing? The difference between testing the product (e.g., squirt gun) vs. testing the system that builds it ✅ The role of automation in development—is code like factory machinery? ✅ How testing connects to broader software and team dynamics—beyond just writing tests ✅ Common pitfalls in testing and how to ensure your tests actually add value ✅ Logical debates vs. ego-driven arguments—how to have productive discussions about TDD 💡 Key Takeaways: 🔹 TDD is often misunderstood—before rejecting it, understand what it really is 🔹 Many developers struggle with writing the right kind of tests—knowing what to test is critical 🔹 Automated tests don’t just verify code; they help manage change and reduce long-term costs 🔹 Good testing and TDD are about more than just code—they’re about communication, clarity, and better software development 📌 Who should watch/listen? If you’re a developer, tester, software engineer, or tech lead who wants to improve your testing skills, understand TDD better, and learn from a Rails testing expert, this episode is for you! 🎧 Subscribe & Listen: Don’t miss an episode! Subscribe to the Mob Mentality Show on your favorite platform: 👉 https://www.mobmentalityshow.com/ 🔥 Join the Conversation! Have thoughts on TDD and Automated Testing? Share them in the comments! Video and Show Notes: https://youtu.be/_kL_tXiNcl4…

The Mob Mentality Show

1
Agile Principle #12: Continuous Reflection & Adjustment in Mobbing 12:33

cách đây 8 weeks trước12:33

12:33

How often should Agile teams reflect and adjust? Is your team on a road with switchbacks but they are not turning the wheel? In this episode of The Mob Mentality Show, we take a deep dive into Agile Principle #12, which states: "At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly." From a Mob Programming perspective, we explore what "tuning and adjusting" really looks like in high-uncertainty, high-interdependence work. Is it like steering a car, constantly making small adjustments, or is it something that requires far less steering? How do different approaches—Waterfall, 2 Week Scrum, and Mob Programming—each handle batch size and feedback loops with continuous improvement? In This Episode, We Discuss: ✅ Agile Principle #12—How it drives continuous improvement in teams ✅ "Regular Intervals"—Comparing Waterfall, 2-week Scrum sprints, and healthy mobbing ✅ Batch Size & Effectiveness—How small adjustments impact team agility ✅ Single vs. Double Loop Learning—Which leads to deeper team growth? ✅ Diversity & Focus—Does learning together accelerate improvement more than learning separately? ✅ The Cynefin Model—Navigating uncertainty and complexity in Agile work ✅ Liminal Thinking—How belief structures and assumptions impact team reflection Many teams go through the motions of retrospectives, but are they truly adjusting their behavior effectively? Join us for this insightful discussion where we challenge assumptions, explore deeper learning, and uncover the best ways to reflect, adapt, and improve as a team. 🎧 Subscribe & Listen: Don't miss this episode! Subscribe on your favorite platform here: 🔗 https://www.mobmentalityshow.com/ 📩 Connect with Us Let us know your thoughts in the comments! How does your team reflect and adjust? Video and Show Notes: https://youtu.be/ikmWgj44g28…

The Mob Mentality Show

1
When TDD Meets R&D: How to Keep Small Steps & Fast Feedback Loops in High Uncertainty 26:10

cách đây 9 weeks trước26:10

26:10

How do you balance small, iterative progress with the vast unknowns of research and development (R&D)? Can test-driven development (TDD) literally or "in spirit" still provide value when you're navigating uncharted territory? In this episode of the Mob Mentality Show, we dive deep into the intersection of R&D Mobbing and software development, exploring real-world scenarios, strategies, and challenges teams face when innovating under uncertainty. What You’ll Learn in This Episode: 🔬 Chris's Journey with Mob Randori & R&D: From "we don’t know what we’re doing" to "we know what we’re doing"—how mob programming helped transform uncertainty into effective delivery. 🛠️ R&D vs. CD? Can teams practice continuous delivery (CD) even when tackling complex, unknown problem spaces? If so, is there a change in what is "delivered"? 📌 Keeping Small Steps & Feedback Loops in R&D: TDD is known for its rapid feedback and endorphin kicks—but how do you retain those benefits when exploring an unfamiliar landscape? 🔄 Adjusting Your Mobbing for the Task at Hand: When should you modify your mob programming approach to fit the nature of research-driven work versus production-level development? 🧗‍♂️ Clean Code Spelunking & Navigating the Unknown: Techniques for digging deep into existing codebases while ensuring safety and maintaining forward momentum. 🚩 Feature Flags & Safety in R&D: How to experiment with new ideas and do Trunk Based Development (TBD) without introducing instability to production. 📊 Transparency, Visualization & Business Buy-in: Addressing stakeholder fear of an "infinite problem space." 🧠 The Inverse of ZOMBIES in R&D Mode: How do you maintain focus, momentum, and value delivery when dealing with high levels of uncertainty? ⚡ Real-Life R&D Success Stories & Lessons Learned: Practical examples of mob programming driving R&D innovation in high-unknown environments. If you’ve ever wondered how to keep experimentation structured, learning fast, and delivery continuous—even when dealing with complex unknowns—this episode is for you! 📌 Watch More Episodes & Subscribe on Your Favorite Platform: https://www.mobmentalityshow.com/ 🔔 Don’t miss future episodes—hit the subscribe button! Video and Show Notes: https://youtu.be/nipbhFopqMM…

The Mob Mentality Show

1
The DDD Dream? A Domain Expert Full-Time in a Mob 🚀 17:28

cách đây 10 weeks trước17:28

17:28

Is the ultimate Domain-Driven Design (DDD) dream having a domain expert fully embedded in a Mob? Or does it come with hidden trade-offs? In this thought-provoking episode of the Mob Mentality Show, we explore the benefits, challenges, and real-world experiences of having a domain expert (or product owner) participate full-time in a Mob—not just as a consultant but as an active driver and navigator. 🔹 What We Discuss in This Episode: ✅ Quick Access vs. Full-Time Participation – Is it better to have a domain expert available when needed or fully immersed in the Mob? ✅ Real-World Stories – Chris shares insights from four product owners with different availability levels and how that impacted effectiveness. Austin reveals what happened when a domain expert became a full-time Mobber. ✅ The Pros of a Full-Time Domain Expert in a Mob – Faster decisions, deeper collaboration, improved knowledge transfer, and more! ✅ Natural Synergy with DDD – How DDD experts seamlessly jump into code naming, improving model alignment. ✅ Testers & Domain Experts: A Similar Integration? – The parallels between merging testers into a Mob and embedding domain experts. ✅ Potential Downsides – Does being in the Mob full-time reduce a domain expert’s ability to stay ahead in their field? ✅ Autonomy & Learning Diversity – How does this setup impact team growth and decision-making? ✅ Is This the DDD Dream? – With fewer moving parts (like event storming), does a domain expert in the Mob make DDD even more effective? ✅ The Power of Different Perspectives – Why having a built-in devil’s advocate can enhance team decision-making. ✅ The Truth About Cryptic Code – Can a domain expert help clarify unclear code in real time? 🎧 Don’t Miss This Insightful Discussion! Hit Subscribe and turn on notifications so you don’t miss future episodes! Find us on your favorite platform here 👉 https://www.mobmentalityshow.com/ What do you think? Would you want a domain expert full-time in your Mob? Drop a comment below! ⬇️ Video and Show Notes: https://youtu.be/7__ghFw_Z3g…

The Mob Mentality Show

1
LLMs, DSLs, and the Art of Generating Generators for Leaner Systems 29:06

cách đây 11 weeks trước29:06

29:06

Can a combo of Large Language Models (LLMs) and Domain-Specific Languages (DSLs) streamline development by automating repetitive patterns across teams? In this Mob Mentality Show episode, we dive deep into the intersection of AI-driven automation, code generation, and lean software development. Join us as we explore: ✅ The "Generator for the Generator" Concept – How AI-powered tools and Mob Programming can create DSLs that automate code generation at scale. ✅ Handling Cross-Domain Development with DSLs – How DSL arguments can be leveraged to generate applications across multiple domains while maintaining usability. ✅ Serverless Infrastructure as Code (IaC) & Auto-Generated Apps – How to use DSLs to automate cloud deployment with Angular or Streamlit apps. ✅ The Challenge of UI/UX in Generated Code – When UI is too generic, does it hurt usability? Can a DSL strike the right balance between automation and user experience? ✅ Regeneration vs. Continuous Development – Should teams work exclusively in the DSL, or also refine the code it generates? How to handle sync issues when regenerating applications. ✅ Turning Docs into Code with a DSL Converter – Automating workflows by transforming team documentation into executable code. ✅ Mob Automationist Role Inception – Is the next evolution of Mob Programming automating the automation? ✅ ZOMBIE Test Generation & Nested Python Dictionaries – How automated testing fits into the DSL-driven workflow and whether a DSL can be as simple as a structured Python dictionary. 🎯 Whether you’re a software engineer, an agile practitioner, or just fascinated by AI-driven development, this episode is packed with real-world insights into DSLs, LLMs, and the future of lean automation. 🔔 Don't miss out! Subscribe to the Mob Mentality Show on your favorite platform: 👉 https://www.mobmentalityshow.com/ Video and Show Notes: https://youtu.be/0q3jaX6_bfw…

The Mob Mentality Show

1
Human & AI Collaboration in Mob Programming with Aaron Griffith and Parker Barrett 53:05

cách đây 12 weeks trước53:05

53:05

Explore the exciting intersection of human collaboration and artificial intelligence (AI) in software development with this insightful episode of the Mob Mentality Show. Recorded for the 2024 UACon Winter: The Future of Product Development Summit on December 10, 2024, Aaron Griffith and Parker Barrett joins Austin to dive deep into how Mob Programming and AI are reshaping the way we build and test software. This episode is packed with practical insights, real-world examples, and actionable strategies for leveraging AI with a mob programming style. Whether you’re an AI enthusiast, a software developer, or just curious about the future of collaboration, this session has something for you. What You'll Learn in This Episode: 🔹 What is Mob Programming? 🔹 The Origin Story of Mobbing with AI – Discover how our human teams began mobbing with AI tools like ChatGPT and GitHub Copilot to enhance software development processes. 🔹 AI-Driven Test Development in a Mob – See how AI can streamline test-driven development (TDD) workflows, making testing faster and more effective. 🔹 Testing with AI to Find ZOMBIES Test Cases (Zero, One, Many, Boundaries, Interface, Exceptional, Simplicity) – Learn how AI tools help identify missing test scenarios and code improvements. 🔹 AI Limitations and Warnings – Understand the ethical, technical, and operational challenges when incorporating AI into your workflows. 🔹 AI Mobbing Demo Highlights: AI-generated Flutter app complete with unit tests. AI-driven identification of ZOMBIES. Automated Continuous Integration/Continuous Deployment (CI/CD) pipelines powered by AI. Why This Episode Matters: As AI tools continue to evolve, understanding how they integrate with collaborative programming methods like Mob Programming and Extreme Programming (XP) is critical for staying innovative in the fast-paced world of software development. In this session, we not only discuss the benefits of AI but also provide a realistic view of its limitations and how to navigate them. Perfect For: Developers and teams exploring AI-powered tools. Agile practitioners and extreme programming enthusiasts. Anyone curious about the future of software development collaboration. Let’s shape the future of collaboration and development together! Video and Show Notes: https://youtu.be/BsFPbYX4WXQ…

The Mob Mentality Show

1
Multi-Mobbing with Extreme Ownership: Should Ensemble Decisions Wait for Outside Approval? 19:40

cách đây 13 weeks trước19:40

19:40

In this thought-provoking episode of the Mob Mentality Show, we dive into the world of extreme ownership within a multi-mobbing environment. What happens when a mob/team wants to make a decision, like extracting a method, refactoring to a new pattern, or reorganizing code boundaries? Should that decision wait for approval from outside teams? Or does extreme ownership mean trusting the mob to act autonomously for maximum flow efficiency? Topics Discussed: Autonomy vs. Consensus: Should mobs prioritize quick decision-making or seek input from external teams? Multi-Mob Context: Exploring the dynamics of multiple mobs interacting and how to handle shared ownership of repositories and projects. Inverse Conway Maneuver: Can designing your organization’s team structures to match the architecture you want your systems to have prevent this problem? Lean Thinking and Efficiency: How waiting for approvals from external owners can create lean wastes. Boundary Flexibility: Should code and team boundaries be rigid or adaptable to changing circumstances? The Monolith vs. Microservices Debate: Is the real issue a technical architecture debate or is the root problem found elsewhere? Scenarios and Examples: A hypothetical comparison of shared ownership in MS Word vs. MS Excel. The impact of Joe Justice’s Law on decision-making and team interactions. The challenge of managing too many communication nodes in multi-team environments. Key Questions Discussed: Is it more valuable to reduce the number of teams interacting with a repo? Should boundaries of ownership evolve with time? How can we balance flow efficiency with healthy collaboration across teams? How does "Nothing in Tech Matters Except XP" impact this discussion? Subscribe and Stay Connected: Don’t miss this insightful episode as we unravel these questions and more! Discover how the principles of extreme ownership and mob programming can transform team dynamics and decision-making processes in software development. 📢 Subscribe to the Mob Mentality Show on your favorite platform: https://www.mobmentalityshow.com . 🔔 Like, comment, and share to join the discussion and stay updated on upcoming episodes! Video and Show Notes: https://youtu.be/rAT-EurLnrI…

The Mob Mentality Show

1
The Poisonous Price of an Unsustainable Pace: Lessons from Software and Sports 25:40

cách đây 14 weeks trước25:40

25:40

In this episode of the Mob Mentality Show, we dive into Sustainable Pace, a core principle of the Agile Manifesto ("Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely"). From software development to youth sports, we explore the massively destructive effects of an unsustainable pace and highlight the transformative benefits of a culture grounded in sustainable practices. 🔥 Key Topics Covered 1. The Massively Destructive Results of Unsustainable Pace How the relentless work rate leads to burnout, dropouts, injuries, and errors. Insights from academic and medical studies showing the devastating effects of unsustainable workloads. Real-world connections to coding bug rates, over-specialization, and emotional exhaustion. Tim Urban's TED Talk ("Inside the Mind of a Master Procrastinator") and its ties to the procrastination monkey, panic monster, and unsustainable pace. Why misalignment between expectations and reality (e.g., unrealistic deadlines) breeds toxicity. Radical Candor's "obnoxious aggression" and it can join forces with unsustainable pace to form a diabolical duo. 2. The Positive Results of a Sustainable Pace Building high-quality, continuous delivery without chaos or burnout. The connection between psychological safety, inclusivity, and long-term success in both teams and individuals. Benefits of diverse experiences, low stress, and personal peace from a sustainable pace. Practical strategies to avoid contributing to toxic work or play environments. Stories from youth sports coaching and tech leadership that illustrate how sustainable pace leads to lasting excellence. 3. Actionable Insights for a Better Future How to shift from a culture of "run fast, burn out" to one of balance, productivity, and joy. The systemic changes needed to foster sustainable pace in tech teams and youth sports organizations. Why adopting sustainable practices isn't just about survival—it's about thriving. 🎙️ Why Listen? Whether you're a tech leader, Agile practitioner, parent, or coach, this episode is packed with actionable advice and thought-provoking discussions. Learn how sustainable pace can unlock continuous learning, higher quality results, and a more fulfilling life. ✅ Subscribe to Stay Updated Don't miss other enlightening discussions! Subscribe to the Mob Mentality Show on your favorite podcast platform or YouTube channel: https://www.mobmentalityshow.com 📢 Join the Conversation What’s your experience with unsustainable pace? How have you built or experienced sustainable practices in your work, team, or community? Drop your thoughts in the comments below and let’s talk! Video and Show Notes: https://youtu.be/bTvjoGosBnw…

The Mob Mentality Show

1
The Power of Diversity: How ‘Mob Anything’ Revolutionizes Product Discovery with Martin Christensen 47:28

cách đây 15 weeks trước47:28

47:28

In this exciting episode of the Mob Mentality Show, we sit down with Martin Christensen, a product transformation coach, to explore the pivotal power of mobbing in product discovery. What You'll Learn in This Episode: Mobbing Product Discovery What is Product Discovery? Understand the fundamentals user value, business value, and technical feasibility. Mob Style vs. Solo User Interviews: Learn how mobbing on user interviews enhances insights through diverse perspectives and how it contrasts with traditional solo interviews. The Benefits of Diversity: Discover why the mantra “Mob Anything” unlocks innovation, faster UI/UX iterations, and fewer lines of code while maintaining focus on user experience. Collaboration, Psychological Growth, and Transformation Barriers to New Methods: Dive into the psychological and organizational obstacles that can hinder teams from adopting mobbing or trying new approaches. Adult Development and Teaming: Martin shares insights on how stages of psychological development and life events can break down egocentrism and foster stronger collaboration. The "No Pain, No Gain" Paradox: Can growth happen without trauma? Discover the nuanced relationship between challenges, growth, and maturity in collaborative environments. Impact of Complexity on Happiness: Unpack how the complexity of problems and overall team happiness affect the ability to work effectively as a mob. Why Watch This Episode? If you’re passionate about product development, user experience, or team collaboration, this episode is packed with actionable insights and relatable stories. From understanding the power of mobbing in product discovery to overcoming barriers to psychological maturity in teams, this conversation will leave you inspired to experiment and grow. 🎙️ Don’t miss out! Subscribe to the Mob Mentality Show today to catch this episode and explore other topics at the intersection of innovation, collaboration, and personal growth. 👉 Watch here or on your favorite platform: https://www.mobmentalityshow.com/ Video and show notes: https://youtu.be/IPYXElnuBns…

The Mob Mentality Show

1
Want to Know Who Else Mobs? Check Out the Companies That Mob Board! 8:26

cách đây 16 weeks trước8:26

8:26

Have you ever wondered who else is adopting mob programming? Or perhaps you’re curious about the diversity of organizations that practice ensemble programming? In this Mob Mentality Show episode, we take a deep dive into the Companies That Mob/Ensemble Program Board, a powerful tool for tracking and sharing insights about organizations, coaches, and educators engaging in mobbing practices worldwide. Join us as we explore the story behind this invaluable resource and its broader implications for the mob programming community. What You’ll Learn in This Episode: Why Track Mobbing? Discover why Chris Lucian started documenting companies and organizations that practice mob programming, beginning with a simple blog post. From Blog to Trello: Learn how this tracking effort evolved from a personal blog to a comprehensive Trello Board, making it easier to manage and share. Uses of the Board: Explore the board’s practical applications, including showcasing the diversity of mobbing practices across countries, industries, and contexts like IoT (Internet of Things), eCommerce, hardware, firmware, software, government, and private sectors. Related Resources: Uncover the connections between this board and other similar initiatives, such as the Software Professional Resources Board and the "We Do TDD (Test-Driven Development)" website. Anecdotal ROI: Hear how this board can serve as anecdotal evidence of the return on investment (ROI) for mob programming from a "just sharing" perspective ( https://justsharing.dev/ ), helping promote its adoption in the software development community. New Categories: Find out about Austin’s updates, which include categories for coaches and professors who practice mobbing. Call to Action: Get inspired to contribute by adding new companies, organizations, or individuals to the board to help grow the global mobbing network. Why This Matters: The Companies That Mob/Ensemble Program Board isn’t just a list—it’s a living resource that reflects the growing diversity and diffusion of mobbing practices worldwide. It’s a tool for saving time, building community, and promoting the Just Sharing mindset. Whether you’re a seasoned practitioner or a newcomer to mobbing, this board helps you connect with others and find inspiration for your own mob programming journey. Get Involved: Want to see the board in action? Check it out here: Companies That Mob/Ensemble Program Board . Subscribe for More Episodes: Don’t miss out on future episodes of the Mob Mentality Show! Subscribe on your favorite platform today: Mob Mentality Show Website . Tune in and discover who else is mobbing—and why it’s transforming the way we work and learn! Video and Show Notes: https://youtu.be/yCB4n-0nxQk…

The Mob Mentality Show

1
Why is XP Not Taught in Many Schools? 26:38

cách đây 17 weeks trước26:38

26:38

Have you ever wondered why Extreme Programming (XP) isn’t commonly taught in schools? In this engaging episode of the Mob Mentality Show, we dive into this intriguing question brought to us by the mob programming community. 🎓 What We Cover: 1️⃣ A Junior Developer's Dilemma: If schools don’t teach XP, does it mean it’s not critical for your career? 2️⃣ Academia’s Pushback: What are professors saying about XP and unit testing? Is XP seen as incompatible with academic goals? 3️⃣ Systems Thinking in Action: Unpacking how a systems-thinking approach (holistic problem-solving) provides clarity on this issue. 4️⃣ The Runner Analogy: How comparing sprinters and cross-country runners sheds light on coding strategies. 5️⃣ Universities vs. Industry Needs: Are schools preparing students for industry or academic research? What should their goals be? 6️⃣ Degree Confusion: Why students struggle to navigate differences between computer science and software engineering programs. 7️⃣ Niche or Necessity? Why XP, a small sector of the software industry, may not get the spotlight it deserves in schools. 8️⃣ Unit Testing's Lone Survival: Is unit testing finding its way into classrooms, but XP is not? 9️⃣ The “Unknown Unknowns” Problem: What happens when students don’t even realize the value XP could bring to their careers. 🔟 Solutions That Work: Experiments and strategies we’ve used to promote XP in university curricula. 💡 Why This Episode Matters: Maintainability in Code: Discover why maintainability is crucial—not just in industry, but even for academic projects. Handling Resistance: Learn how educators can introduce XP despite opposition from traditional academic mindsets. Spotlighting Success: Shout-outs to universities doing XP right and what others can learn from them. Academia-Industry Collaboration: Insights from years spent on professional committees advocating for XP. 📌 Who Should Watch This Episode? Students: Discover why your curriculum may overlook XP and how to build the skills yourself. Educators: Get inspired to bring XP into your classrooms and navigate institutional challenges. Industry Professionals: Understand the gap between academia and industry, and what it means for hiring new grads. Join us as we explore the challenges and opportunities of integrating XP into education. With actionable insights, engaging analogies, and practical advice, this episode is packed with ideas to spark change. Video and Show Notes: https://youtu.be/CidbB_SBGl0…

The Mob Mentality Show

1
Complex Adaptive Organizations, Org Topologies, and FAST Agile with Ariel Pérez 46:09

cách đây 18 weeks trước46:09

46:09

In this thought-provoking episode of the Mob Mentality Show, we are joined by Ariel Pérez to explore the fascinating intersection of Complex Adaptive Organizations, Organizational Topologies, and the FAST Agile Framework. Together, we dive into the challenges and opportunities of modern software development and organizational dynamics, offering actionable insights for leaders, teams, and anyone navigating complexity in their work. Highlights from the Episode... Complex Adaptive Organizations and FAST Agile: Manufacturing vs. Software Development: Why building the same product repeatedly differs from creating custom software . Complexity Theory in Software Development: How unpredictable side effects shape outcomes and the pursuit of predictability in organizations. Fixed Scope and Fixed Date: Are they real business needs, or just external motivators? What are their long-term impacts on quality and delivery? Theory X vs. Theory Y (management theories): How a leaders' management principles and practices influence autonomy, trust, and collaboration. Dynamic Teams in FAST Agile: The pros and cons of adapting teams dynamically to match work needs versus forcing work into rigid team structures. Story of Transitioning to FAST: A tale of initial resistance to the FAST Agile approach and the eventual embrace of its benefits. Building a Culture of Experimentation and Learning: Experimentation as a Foundation for Innovation: How to test hypotheses in product development and team practices without compromising quality. From Fear to Trust: Encouraging experimentation in new teams or under new leadership while creating safety for bold ideas. Practical Experiments: Implementing small feature flags, A/B testing (comparing two versions in production), and time-limited trial runs to foster innovation. Respect and Radical Candor: Building trust through open communication, mutual respect, and the occasional dose of healthy banter 😅. Risks and Controls: A Never-Ending Game of Whack-a-Mole: Balancing Risk and Control: How risk-heavy environments lead to more controls (e.g., CAB—Change Advisory Board, PR—Pull Request) and the ripple effects of other risks these controls create. Holistic Thinking: Why addressing one risk often introduces others and how to manage risk without stifling agility. Mob Programming as a Solution: Handling emergency changes safely and collaboratively without falling into the trap of excessive gatekeeping. Key Takeaways: Embrace complexity and adapt dynamically to navigate unpredictable challenges. Optimize for learning through experimentation and apply these insights to real-world problems. Avoid control-heavy environments that stifle innovation and agility by thinking holistically about risks. Join us as we unpack these ideas and share strategies to foster a responsive, trust-based culture in your teams and organizations. 🎧 Don’t miss this episode! Subscribe to the Mob Mentality Show on your favorite platform: https://www.mobmentalityshow.com/ FYI: Video and more show notes: https://youtu.be/ghzOSV4waIo…

The Mob Mentality Show

1
Is Some Refactored Code Actually Better? Facilitating Disagreements Between Humans and Robots 17:07

cách đây 19 weeks trước17:07

17:07

Is some refactored code truly better—or is it just a matter of taste? In this episode of the Mob Mentality Show, we explore the debate: Is some refactoring a subjective preference or an objective improvement? Join us as we dive into the fascinating world of refactoring, where code quality, team dynamics, and even artificial intelligence (AI) come into play. Here’s what we discussed: The Ice Cream Debate: The story of a team/mob navigating a series of refactorings and asking, Are these changes about style, like preferring chocolate over vanilla? Or is there an objective improvement in the code? Cognitive Load, Cyclomatic Complexity, and More: How refactored code impacts key factors like cognitive load (mental effort required to understand code), cyclomatic complexity (a measure of the number of independent paths through a program), readability, and maintainability. Copilot AI's Take: Results of analyzing “before and after” versions of refactored code using Copilot AI (a large language model or LLM trained for coding). Does the AI agree with human developers? Gray Areas vs. Black-and-White Decisions: How much of refactoring is clear-cut improvement versus a matter of debate? Coaching Through Disagreements: Strategies to coach a team through potentially heated refactoring disagreements. Should you stick to principles or let the team run experiments in production against the principles? Decision-Making Tactics: How to align on contentious refactoring decisions. Should you flip a coin, follow a guiding principle, or defer to team consensus? Principles and North Stars: Identifying which coding principles matter most to your team and using them as a decision-making anchor. Dealing with Apathy: How to engage team members who are indifferent to coding principles and quality debates. 7 Habits of Highly Effective People: Applying Stephen Covey’s timeless principles to facilitate productive refactoring discussions and team collaboration. Diversity of Opinion as a Strength: Embracing different perspectives to make your team or mob/team stronger and more innovative. Radical Candor vs. Safe Experiments: Balancing direct feedback with the freedom to experiment—even if it means running tests in production. “Stop the Line” Moments: Deciding when a refactoring disagreement is serious enough to halt progress versus letting safe experiments play out. Whether you’re a developer, team lead, or software architect, this episode is packed with insights to improve your approach to refactoring and team dynamics. 👉 Don’t miss this thought-provoking discussion! Video and Show Notes: https://youtu.be/s2bl7dFAIV0…

The Mob Mentality Show

1
Is Scaling the Root of All Evil? 11:32

cách đây 20 weeks trước11:32

11:32

What happens when teams, codebases, or systems scale beyond their limits? In this thought-provoking episode of the Mob Mentality Show , we tackle this hyperbole: “Is scaling the root of all evil?” We explore how the challenges of scale —in team size, code complexity, and even societal structures—might be the culprit. 💡 Key Discussion Points: Defining Scale Across Contexts: How does scale impact teams, classrooms, codebases, and more? Innovation vs. Scale: Does scaling stifle the spread of good ideas, principles, and practices (e.g., in law, culture, or workplace norms)? Interpersonal Challenges: Why do interpersonal problems grow exponentially in larger groups? Code Quality and Scale: Does a larger codebase inherently lead to lower quality? Focus and Attention: How does scale dilute individual and team focus? What happens to attention in scaled systems? Second-Order Effects: Are rigid systems designed to handle scale unintentionally creating harmful side effects—and even side effects of those side effects? Experimentation and Innovation: How do rigid systems inhibit experimentation, and why does this matter for growth and innovation? Descaling as a Solution: Are the best solutions to scaling problems simply about reducing scale? Inverse Conway Maneuver: Exploring this organizational design concept and its relevance to scaling. Lessons from Coaching: How scaling challenges in youth baseball practices compare to leading software development teams. 🎯 Why You Should Watch/Listen This episode touches on the consequences of uncontrolled growth, from technical issues in software engineering to cultural and organizational challenges. Learn why "descaling" could be the key to improving focus, quality, and innovation in your team or organization. Plus, discover how mobbing (collaborative software development) naturally counters the pitfalls of scaling. 📢 Don’t miss out! Subscribe now on your favorite platform: https://www.mobmentalityshow.com/ Video and Show Notes: https://youtu.be/YLeyRHcI-eI…

The Mob Mentality Show

1
Mob Programming Meets Neuroscience: Exploring Brainwaves and Team Dynamics with Mike Bowler 49:15

cách đây 21 weeks trước49:15

49:15

Join us in this exciting episode of the Mob Mentality Show as we dive deep into the fascinating intersection of mob programming, neuroscience, and team dynamics with the insightful Mike Bowler! Mike brings over a decade of experience facilitating mob programming sessions across hundreds of teams and countless experiments. Whether you're a software developer, team coach, or collaboration enthusiast, this conversation will leave you with actionable insights and inspiring takeaways. 🔍 What We Discuss: - A Different Approach to Facilitating Mob Programming Sessions - The Neuroscience of Psychological Safety and Mobbing - Team Flow States and Brainwave Activity - About Mike Bowler 📢 Don’t Miss Out! Subscribe to the Mob Mentality Show on your favorite platform to learn more about innovative collaboration techniques and team success. 🔗 Find us here: https://www.mobmentalityshow.com Video and show notes: https://youtu.be/okeAxvRggVc…

The Mob Mentality Show

1
From Fear to Flow: Coaching Code Reading and Refactoring 20:27

cách đây 22 weeks trước20:27

20:27

What does it take to shift from fear to flow when reading and refactoring code? In this episode of the Mob Mentality Show, we dive deep into **"Paradigms of Code Reading"**, exploring the mindsets and techniques that shape how developers approach software understanding. Whether you're navigating legacy code or striving for clean, maintainable designs, this discussion offers actionable insights for individuals, pairs, and mobs alike. ### What You’ll Learn in This Episode: - **Code Reading Paradigms**: Discover the two ends of the spectrum: - **Understand Every Line**: Keeping every detail in your head. - **Extreme Abstraction Zen**: Focusing only on the current module or method. - **AB Testing in Code Reading**: Insights from live experiments on how pairs and mobs read and understand code. - **The Role of Trust**: How levels of trust in variable names, methods, and classes influence reading strategies. - **Overcoming Fear and Skepticism**: What causes developers to ignore method names or distrust the knowledge baked into the code? - **Cognitive Load and Flow Efficiency**: Learn how reducing cognitive load through small, fast tests can lead to more effective coding sessions. - **Code Reading Clubs** - **Coaching Toward Abstraction Zen**: Practical strategies to influence and support others in adopting better reading and refactoring paradigms. - **Embracing Skeptics**: The value of radical candor, genuine curiosity, and visual aids like diagrams in addressing fear and building trust. ### Key Takeaways: - Refactoring starts with trust - Genuine curiosity can replace complaints, transforming how teams collaborate and learn. - Drawing pictures and visualizing code can unlock new perspectives and improve comprehension. - Skeptics are not obstacles—they're opportunities for deeper conversations and better design. Whether you're a seasoned software engineer, a pair programming enthusiast, or new to mob programming, this episode will provide you with practical tools and thought-provoking questions to enhance your coding practice. 💡 **Want to stay ahead in your software journey?** Don't miss this deep dive into the cognitive, emotional, and technical aspects of reading code. 🔗 **Subscribe to the Mob Mentality Show**: Get notified as soon as this episode drops! Available on all major platforms: 👉 https://www.mobmentalityshow.com/ 🎧 Tune in to unlock new paradigms for code reading and refactoring. Let’s move from fear to flow together! Video and Show Notes: https://youtu.be/pXEp6jBeycs…

The Mob Mentality Show

1
The Software Professional Resources Board 16:45

cách đây 23 weeks trước16:45

16:45

In this episode of the Mob Mentality Show, we dive into our Software Professional Resources Board, a dynamic Trello-based hub designed for software professionals looking to enhance their learning and collaboration in the industry. Join us as we share the board’s origin story and our journey in creating a comprehensive resource for everything from Extreme Programming (XP), mobbing, and leadership to cloud infrastructure, agile retrospectives, lean principles, and much more. ### What Makes Our Board Unique? We start by exploring why we chose **Trello** for our resource board and how it has become a cornerstone for organizing, sharing, and discovering knowledge. With its flexibility, Trello enables us to create an easily navigable environment, where resources are not only organized but can also be searched, linked, and explored across various software domains. Our conversation touches on other similar boards we’ve seen, like our popular "Retrospective Techniques for Coaches, Scrum Masters, and Facilitators" board, as well as spin-offs we’ve created for specific topics. ### A Variety of Topics Our board covers a broad spectrum of topics that are essential for modern software professionals, including **mobbing**, **refactoring**, **leadership**, **Infrastructure as Code (IaC)**, **agile** practices, and more. With resources curated for both technical and strategic learning, the board has become a go-to reference for articles, blog posts, videos, academic papers, book links, and quotes on various disciplines within software development. ### How We Use the Board for Continuous Learning Discover how we leverage the board not only to organize information but to foster continuous learning. We discuss Chris’ “community-supported learning binges” and our process for capturing insightful book quotes and key takeaways, turning the board into a knowledge-sharing powerhouse for software teams and individual contributors alike. ### Refactoring the Mind: Evolving the Board to Stay Relevant Our discussion also delves into the concept of "refactoring my mind by refactoring the board"—an idea about how reorganizing knowledge can improve our mental clarity and adaptability in complex projects. This involves regularly revisiting, reshaping, and expanding board content to reflect the latest insights and trends in software development, keeping it a living, breathing resource for our community. ### The Impact of Public Knowledge Sharing One of the most inspiring aspects of this board is its role in **public knowledge sharing**. We highlight feedback from the community, stories of how others have used the board in their professional journeys, and our own experiences with learning in public. By sharing this resource openly, we invite others to benefit from it, create connections, and add to the body of knowledge that supports software development excellence. Whether you’re a developer, coach, Scrum Master, or technical leader, this episode offers valuable insights into how to create and use a resources board to drive personal and team growth. Listen in for tips on organizing knowledge, capturing valuable insights, and using community feedback to make a resource board that truly enhances your software development journey. ### Topics Discussed: - The board's origin story and why we chose Trello - Organizing, searching, and sharing resources in Trello - Similar boards, including "Retrospective Techniques for Coaches, Scrum Masters, and Facilitators" - Variety of topics: mobbing, XP, leadership, IaC, agile, cloud, business, tech, retrospectives, and more - Types of media: articles, blogs, videos, book quotes, academic papers, and beyond - Spin-off boards and community learning sessions - Feedback from the community and lessons for public knowledge sharing **Subscribe on YouTube or your favorite podcast platform to catch this episode and more!** Video and Show Notes: https://youtu.be/GmfWWiIeaVY…

The Mob Mentality Show

1
Continuous Delivery to Cappuccinos: Jeff “Cheezy" Morgan’s Journey from Agile DevOps to Lean Cafés 51:22

cách đây 24 weeks trước51:22

51:22

In this Mob Mentality Show episode, we dive into the journey of Jeff “Cheezy” Morgan, a coach in Continuous Delivery (CD) and lean thinking. Known for his role in advocating for CD within companies, Jeff shares how his experiences with software development and his recent shift into the café business have shaped his philosophy on people and just-in-time. This discussion explores how Jeff’s approach to Agile and CD evolved, his journey into Extreme Programming (XP), and how mob programming impacted his perspective on teamwork and Continuous Integration (CI). **Jeff’s Agile and CD Journey** We start with Jeff’s introduction to Agile, discussing the early days of his career when dev practices didn’t include CD and the impact of adopting CD in high-stakes projects like Y2K. Jeff describes how learning from Thoughtworks influenced his views on XP and CD, and how he became an advocate, eventually taking CD to different organizations. He also shares what it was like discussing with Woody Zuill and Llewellyn Falco and reflects on the transformative role mob programming has played in his career. **From Pairing to Mobbing** For Jeff, mob programming was not initially appealing, but over time it became his preferred approach for helping teams. We explore how mobbing enhances CI, tightens communication, and fosters collective learning. Jeff explains how mobbing enables "just-in-time" discussions that align teams on what to build and how it allows real-time feedback on other team members’ learning. Jeff also examines the transition from pairing to mobbing, the challenges of mob programming with CI/CD, and why mobbing helps him “get the whole system in the room” for tackling complex problems. **Quality Without QA?** We dive into the controversial idea of achieving high quality without traditional Quality Assurance (QA). Jeff opens up about years spent wrestling with the role of QA in Agile/CD environments and shares experiments with “test-infected” developers—who took full ownership of quality. He reflects on the pitfalls of relying on “heavyweight” traditional QA processes and automated tests, which often create lean waste, add handoffs, and introduce brittle, flakey tests. Jeff and hosts Austin and Chris discuss whether “shift left” is merely a shift away from QA, the Deming Red Bead experiment’s relevance, and whether there’s a happy journey for QA professionals on CD teams. **Applying Lean to Cafés** Outside the tech world, Jeff has found a second passion—running cafés. We discuss how owning two cafés influenced Jeff’s perspective on Lean thinking and Agile principles. From supply chain issues during COVID to needing backup suppliers, Jeff discusses if “just-in-time” challenges in the café world mirror software development. He shares valuable insights about hiring, managing consistent delivery, and applying Lean principles to run a resilient business. Additionally, Jeff and Chris exchange stories on chip shortages and if Lean can help address real-world supply chain issues. **More from Jeff** Finally, we tackle some big questions: What does DevOps mean in today’s Agile world? Should “DevOps” be responsible for shielding organizations from developers? How does Test-Driven Development (TDD) factor into DevOps scripts, and can mobbing help break down silos that traditionally separated devs, ops, and QA? Join us for this wide-ranging conversation with Jeff “Cheezy” Morgan to uncover actionable insights for anyone involved in Agile, CD, DevOps, or Lean. Whether you're in software, QA, or running a small business, this episode is packed with valuable takeaways on quality, learning, and resilience. Video and Show Notes: https://youtu.be/OJ5d6qLIQRY…

The Mob Mentality Show

1
The Discovery of Ignorance in Product Development: Time for a Smarter Way to Deliver Customer Value with Gary Cohen 50:47

cách đây 25 weeks trước50:47

50:47

In this episode of the Mob Mentality Show, join us as we delve into "The Discovery of Ignorance in Product Development: Time for a Smarter Way to Deliver Customer Value" with our special guest, Gary Cohen. Drawing on his rich experience across diverse sectors—from government agencies to startups—Gary brings a wealth of insight into optimizing product discovery and delivery for true customer impact. ### **Key Topics Explored: The Product Discovery and Delivery Intersection** Even if a team is familiar with the 80/20 rule (e.g., where 80% of features go unused), how does it determine the right 20% to deliver? Gary shares strategies to tackle this challenge, advocating for a shift from traditional roadmap fixation to embracing dynamic, continuous discovery that keeps customer value at the forefront. Together, we examine the effectiveness of "strict" roadmap discipline (the practice of adhering to set timelines and objectives) and if it becomes a barrier to true innovation and customer value. We also briefly touch on the FAST framework and its relevance to product discovery, emphasizing how collective discovery through mobbing allows teams to stay closer to evolving customer needs. ### **The Role of GenAI in Modern Product Development** Is AI is reshaping product discovery? We explore how GenAI can be a collaborative asset for mobs, not only for code development but also for bringing value by uncovering insights into customer behavior and streamlining feature prioritization. We compare "introverted" AI and "extroverted" AI in mob environments and discusses how developing refined AI inquiry skills is key to leveraging AI’s full potential. From training mobs in nuanced prompt engineering to using AI to help drive a more lean delivery, we share ways to maximize AI's impact while maintaining expert human oversight. ### **Bootstrapping Pair and Mob Programming in Individualist Cultures** Transitioning to collaborative programming environments such as pair or mob programming can be challenging, especially in workplaces with a culture of individuality. We offer quick tips on how to bootstrap these methods, from creating a safe space for experimentation to aligning incentives via a peer promotion process. By using context sensitive analogies, how can we influence others in the org to consider jumping into the highly effective world of mob programming? ### **Unpacking Behavioral Expectations: A Smarter Approach to Product Decisions** Beyond the technical, we look at the behavioral side of product monitoring, asking, “What responses do we expect from our users?” Gary emphasizes the importance of behavioral prediction in discovery, cautioning against information bias and providing ways to gauge responses to feature experiments in real-time. We highlight the importance of monitoring usage data and what it reveals about customer engagement—whether a feature elicits a “wow” or a mere “meh.” ### **Takeaways for Product Managers, Engineers, and Innovators** From continuous discovery to leveraging the art of AI prompting, Gary Cohen’s insights provide actionable advice for product managers, developers, and cross-functional teams who are ready to rethink their approach to product development and delivery. Whether you're looking to reduce waste, increase customer value, or integrate mob programming and GenAI into your workflow, this episode offers some experiments to try in your journey to achieve product success. Don’t miss this engaging discussion filled with actionable strategies, insightful anecdotes, and forward-thinking approaches to innovation! Video and Show Notes: https://youtu.be/od7E_M9B6gI…

The Mob Mentality Show

1
Goal-Centricity and Beyond Test First with Kyle Griffin Aretae 45:33

cách đây 26 weeks trước45:33

45:33

In this exciting episode of the Mob Mentality Show, we are joined by Kyle Griffin Aretae to dive deep into the nuances of Test-Driven Development (TDD) and the crucial concept of "Goal-Centricity" in Agile practices. Kyle breaks down why TDD is so much more than just "test first" and challenges common misconceptions about this widely used development practice. If you're a software developer, Agile enthusiast, or just someone looking to refine your team's development processes, this episode is packed with insights you won't want to miss. We explore why treating TDD as merely writing tests first misses the larger picture and how adopting a broader, more progressive approach can help your team build better, more maintainable software. Kyle shares his thoughts on the primary value proposition of TDD, focusing on **fast feedback loops** and the **refactor step** at least every 5 minutes. He explains how smaller, healthier TDD cycles allow developers to stay nimble and avoid the trap of feedback loops that last 30 minutes or more. Thus, when fast feedback loops with constant refactoring are in place as the foundation, then the "test first" aspect of TDD really shines. Kyle also sheds light on common pitfalls, such as the misunderstanding of what it means to "do TDD" when developers claim they have 8 unit tests on 50,000 lines of code. We discusses the difference between **Cargo Cult XP (Extreme Programming)** and the real deal, as well as the critical role of **decoupling code** so tests can run in 5 seconds or less. A key takeaway from this episode is the impact of **social programming**, TDD, and **CI/CD (Continuous Integration/Continuous Delivery) pipelines**. We explain the importance of the "Pipeline First" principle when writing new code. We then dive into Kyle's most controversial take on TDD: the idea that creating a **mini-plan** (a rough roadmap of what to do next) before writing tests might actually be more beneficial than strictly adhering to "test first." This, Kyle argues, leads to more robust code when integrated into strong social programming practices. We also touch on the application of **Maslow's Hierarchy of Needs** to TDD and the importance of satisfying basic development needs (like fast feedback and clean code) before tackling more complex issues. The episode continues with a discussion on the intersection of **Goal-Centricity** and Agile. Kyle questions whether Agile methods are effective without first agreeing on a clear goal. We explore scenarios where goals are unclear or where methods are imposed without understanding the desired outcomes. Kyle shares a fascinating example of a code freeze during "Black Friday" and the unintended consequences of such decisions. We also reference a powerful quote by **Deming**, "A goal without method is cruel," explaining how the opposite can be just as problematic. Throughout the conversation, we dive into the importance of aligning goals between management and development teams, avoiding the common trap of blindly delivering fixed requirements for bonuses, and how real Agile success comes from alignment on solving customer problems, not just ticking off tasks. Kyle emphasizes the need to start with a clear understanding of what you're trying to achieve before applying any method, whether it's Scrum or TDD. Don't miss out on this thought-provoking episode filled with actionable insights on TDD, Agile, and effective software development. Subscribe today and tune in to hear Kyle Griffin Aretae's unique take on how to elevate your development practices! Video and Show Notes: https://youtu.be/S7K8lSibmII…

The Mob Mentality Show

1
From Code to Culture: Chesterton’s Fence vs. Five Monkeys Experiment 16:45

cách đây 27 weeks trước16:45

16:45

In this episode of the Mob Mentality Show, we explore the profound concept of "Chesterton’s Fence" and how it applies to software development and organizational culture. Chesterton’s Fence refers to the idea that before removing or changing a rule, tradition, or practice, one must first understand why it was put in place. We dive into this principle, discuss real-world coding examples, and contrast it with the famous "Five Monkeys Experiment," which explores how behavior and practices can irrationally persist even when the original purpose is forgotten. 🔑 **Key Topics Discussed**: - **Chesterton's Fence**: Learn the origin and meaning behind Chesterton's classic quote: "The more modern type of reformer goes gaily up to it and says, 'I don't see the use of this; let us clear it away.' To which the more intelligent type of reformer will do well to answer: 'If you don't see the use of it, I certainly won't let you clear it away. Go away and think. Then, when you can come back and tell me that you do see the use of it, I may allow you to destroy it.'" Discover why this concept is critical in both software development and team culture. - **Applying Chesterton’s Fence to Code**: We walk through a real-world example of legacy product code. Should you refactor, delete, or preserve existing code? Explore how understanding the original intent of code, especially in larger systems, can prevent costly mistakes. - **When to Delete Unit Tests**: What happens when a unit test no longer seems relevant or helpful? We explore how the Chesterton's Fence principle applies to testing, discussing whether old tests should be removed or maintained, and how to balance thoroughness with agility. - **Five Monkeys Experiment**: Chris Lucian shares insights from the famous psychological experiment that demonstrates how practices can become entrenched even when the original purpose is long forgotten. This complements the discussion of Chesterton’s Fence by examining how some habits and behaviors persist without rationale. We discuss strategies for assessing when it's time to dig deeper or when it's acceptable to move forward without full understanding. While it's important to understand why something exists, can too much time be spent analyzing before making changes? - **Domain-Driven Design (DDD) and Behavior-Driven Development (BDD)**: We explore how principles from DDD and BDD can help teams bake the purpose and intent directly into code, making it easier to understand why a particular rule, function, or test exists in the first place. By the end of the episode, you’ll gain a deeper understanding of how Chesterton’s Fence and the Five Monkeys Experiment apply to your day-to-day decisions in software development, testing, and even team dynamics. Whether you’re dealing with legacy code, outdated tests, or long-standing team practices, this episode provides practical insights to help you make thoughtful, informed decisions. 🎥 **Subscribe and Stay Updated**: Don't miss this insightful episode! Be sure to subscribe to the Mob Mentality Show on your favorite podcast platform or YouTube. Video and Show Notes: https://youtu.be/a2bdNOsM_r0…

The Mob Mentality Show

1
Is All CD/CD Pipeline Code Instant Legacy Code? 15:28

cách đây 28 weeks trước15:28

15:28

In this Mob Mentality Show episode, Chris Lucian and Austin Chadwick dive into the complexities of modern CI/CD (Continuous Integration / Continuous Delivery) pipeline code and IaC (Infrastructure as Code), exploring why these critical components of software delivery often exhibit the same problematic attributes as classic Legacy Code. Drawing inspiration from Michael Feathers' seminal book *Working Effectively with Legacy Code*, they analyze the paradox of cutting-edge DevOps practices turning into technical debt almost as soon as they're written. ### Episode Highlights: - **CI/CD Pipeline Code and Legacy Code Parallels**: Why does so much CI/CD and IaC code resemble legacy code? Despite being crucial for continuous delivery and automation, CI/CD pipelines can become fragile, difficult to change, and filled with technical debt if not handled carefully. Austin and Chris discuss why this phenomenon is so common and what makes the codebases for CI/CD pipelines especially prone to these issues. - **“Edit and Pray” vs. TDD Confidence**: Do your CI/CD changes feel like a roll of the dice? Chris and Austin compare how the lack of test-driven development (TDD) practices in CI/CD code leads to “edit and pray” scenarios. They discuss the confidence that TDD brings to traditional application development and how applying similar principles could reduce fragility in CI/CD code. - **The Pitfalls of YAML in IaC**: Is the problem inherent to YAML? The hosts explore whether the complexity of YAML syntax and configurations is the root cause of the brittleness often found in IaC. They provide real-world examples of IaC configurations that suffer from high cyclomatic complexity—making them feel more like full-blown applications rather than simple configuration files. - **Fear of Change in CI/CD and IaC**: Why are developers often afraid to modify CI/CD pipeline code or IaC? Chris and Austin highlight the psychological aspects of fragile infrastructure—where fear of unintended consequences and lack of fast feedback loops result in slower iterations and more bugs. They explore why these codebases are often re-written from scratch instead of extended and safely enhanced. - **Reducing Fragility through Experiments**: The episode features a recent experiment where CI/CD pipeline code was developed in Python using TDD and separation of concerns. This case study reveals the pros and cons of less YAML and a shift towards more code-based "configurations." Could this approach be a solution to reducing brittleness in IaC and pipelines? - **A World Without Brittle Pipelines?**: Imagine a world without fragile pipelines and brittle configuration files. Chris and Austin discuss strategies to move towards more resilient infrastructure and how teams can focus on improving feedback loops, reducing complexity, and enabling safer, faster CI/CD iterations. Join Chris and Austin as they explore these and other crucial topics that are impacting DevOps teams around the world. Whether you're struggling with high bug rates in your pipelines, slow feedback loops, or simply want to better understand how to manage the complexity of modern infrastructure, this episode is for you! Video and Show Notes: https://youtu.be/3Cs-j055b9g…

The Mob Mentality Show

1
The Dark Side of Metrics: Goodhart’s Law, Cobra Effect, and the Metrics That Damage Teams 14:49

cách đây 29 weeks trước14:49

14:49

In this episode of the Mob Mentality Show, we explore the unintended consequences and pitfalls of relying too heavily on metrics with a dive into Goodhart’s Law. If you’ve ever wondered why well-intentioned measurements can backfire and cause harmful behaviors in software development, leadership, and beyond, then this episode is for you! **What is Goodhart’s Law?** Goodhart’s Law states that “When a measure becomes a target, it ceases to be a good measure.” This means that when metrics are used as goals, people tend to optimize for the metric itself rather than the underlying value or outcome it represents. **How Can Metrics Destroy Collaboration?** Chris shares an intriguing story about two teams set up to compete against each other, only to find that the focus on “winning” metrics led to a breakdown in communication and collaboration. Instead of fostering teamwork, the metrics created silos and a toxic environment. **Examples of Bad Metrics in Software Development** We go through specific metrics that have led to bad behaviors in software teams, such as: - **Test Coverage Metrics**: How a narrow focus on test coverage can lead to tests that do nothing but improve the metric, without actually asserting anything or improving software quality. - **Points-per-Person Metrics**: Why measuring productivity at an individual level (e.g., story points completed per person) damages team dynamics and led to cutting corners. **Are There Any Good Metrics?** Is it possible to use metrics without falling into the Goodhart’s Law trap? We discuss whether certain collective measures like **DORA Metrics** can provide value without the same issues. **Metrics for Conversations, Not Evaluation** One key takeaway is the distinction between metrics that trigger healthy conversations vs. those used to make evaluative judgments of a team from a distance. When metrics become evaluative rather than formative, they risk distorting behaviors and eroding psychological safety. **Leading Measures vs. Lagging Measures** We also touch on insights from *The 4 Disciplines of Execution* and its perspective on leading measures vs. lagging measures. **Managing Teams and Incentives at Scale** Finally, we tackle the challenge of managing people and teams at scale. Incentive structures that overemphasize metrics can lead to counterproductive behaviors, burnout, and loss of motivation. We emphasize the anti-pattern of metrics-driven management without side-by-side in-context coaching. If you’ve ever experienced the pitfalls of metrics-driven environments or are seeking ways to improve measurement practices in your teams, this episode is packed with lessons learned, cautionary tales, and actionable advice. Don’t miss it! Video and Show Notes: https://youtu.be/MiySzmDRYA8…

The Mob Mentality Show

1
How Mob Programming Dissolves the Ego to Boost Team Function: A Conversation with Michael K Sahota 53:42

cách đây 30 weeks trước53:42

53:42

In this insightful episode of the Mob Mentality Show, we sit down with Michael K Sahota to dive deep into the transformative power of **Mob Programming** and **Pair Programming** in dissolving the ego and enhancing team dynamics. Michael shares his unique perspective on how mobbing/pairing can lead to profound psychological shifts, ultimately boosting team function, empathy, and humility. ### Key Highlights: **Pair/Mob to Dissolve the Ego and Increase Team Function** - Michael discusses the **primary goal** of a mob or pair session, revealing how it goes beyond just writing code or learning new techniques. It’s about dissolving the individual ego and fostering a collective, empathic mindset that benefits the entire team. - We explore Michael’s **personal journey** with his ego, offering a candid look at how pairing/mobbing have helped him grow both personally and professionally. - What is the most **significant outcome** of mobbing/pairing beyond the immediate code or learning? Michael explains how the real magic happens when team members listen to each other and take turns, creating a powerful forcing function for collaboration and psychological safety. - We dive into the **psychological processes** that occur during mobbing, including the death of "fear-based clinging" and how healing the ego leads to deeper empathy and humility. Michael offers anecdotes on how mobbing helps resolve internal conflicts and improve relationships—both at work and beyond. - How much time should be allocated for **production** versus focusing on **production capability**? Michael discusses how to strike the right balance between learning and output, avoiding over-indexing on either side. - A unique **"learning theft"** example highlights why juniors should be prioritized during experiments, while senior developers are encouraged to go last—except when it comes to admitting mistakes, where the inverse applies. **Pair/Mob for Production Capability and Beyond** - Michael shares his thoughts on balancing the **development of production capability** with immediate production needs. He explains how overinvesting in production at the expense of capability can destroy long-term results. - We explore how improving production capability with a solid **ROI** can often yield results within a quarter, but must be continually nurtured through retrospectives and lean thinking. - Breaking the cycle of **overinvesting in production** under intense pressure is a major challenge for many teams. Michael shares stories of how transparency in communication, both within and outside the team, can help break this cycle. - Michael introduces the concept of building **culture bubbles** and we share contrasting ideas on how much courage is needed for these bubbles. - We also discuss the **HIPPO effect** and how mobbing can disrupt this dynamic by emphasizing experimentation and collective decision-making rather than deference to authority. - Finally, Michael ties it all together by emphasizing the role of **humility**. No one is a flawless expert, and through mobbing/pairing, teams can build a habit of asking for help and embracing the idea that everyone, regardless of experience, has something to learn and improve. ### Why You Should Watch: This episode is a must-watch for anyone involved in **software development**, team dynamics, or leadership. Whether you're interested in improving psychological safety, fostering team empathy, or enhancing production capability, Michael K Sahota's insights on mobbing and ego dissolution will help you rethink how teams work together. It’s about more than code—it’s about creating a culture of **trust, engagement**, and continuous improvement. Video and Show Notes: https://youtu.be/Wj2hYGMei8s…

The Mob Mentality Show

1
The Nuances behind SRP, YAGNI, DRY, and #NoEstimates with Dave Copeland 49:18

cách đây 31 weeks trước49:18

49:18

In this episode of the Mob Mentality Show, we are excited to have Dave Copeland share his experiences in the world of agile development, focusing on the critical nuances behind well-known principles such as SRP (Single Responsibility Principle), YAGNI (You Aren’t Gonna Need It), DRY (Don’t Repeat Yourself), and the often-debated #NoEstimates approach. Drawing from his journey transitioning from government waterfall projects to agile methodologies at a startup, Dave kicks off a discussion with invaluable lessons on how teams can avoid misunderstanding and misapplying agile aphorisms, or avoid the pitfalls of following agile aphorisms too woodenly. ### The Dangers of Following the Literal Words of Agile Aphorisms? Have you ever seen a team stuck arguing over what SRP or SOLID (Single Responsibility, Open-Closed, Liskov Substitution, Interface Segregation, Dependency Inversion) truly means? Dave explains how teams can misinterpret these catchy phrases, leading to confusion, low cohesion, improper coupling, and poor decision-making. We dive into real-world examples from Dave’s experience, discussing when it's okay to duplicate code and when it's not, the delicate balance between over-engineering and under-engineering, and the importance of nuance in agile practices. ### "Just Sharing" vs. Universal Recommendations Is it wise to blindly follow every "recommendation" from an agile coach, or is there room for discussion, experimentation, and adaptation? With Dave we tackle the common issue of semantic diffusion. We explore how teams can navigate complex situations and adapt agile and lean principles to their unique contexts. ### Organizational Change and Safe Learning Environments We bring in the “Reading Rainbow” analogy and other examples to illustrate how organizational change needs to be gradual, allowing for nuanced learning. We also emphasize the importance of creating an environment where team members can safely fail while being guided by experienced developers in real-world contexts. Whether you’re scaling a team or trying to stack the deck with the right mix of skills, actionable strategies for fostering growth are discussed. ### Estimates, #NoEstimates, and Dealing with Uncertainty The conversation gets even more interesting as we delve into the jarring #NoEstimates and its sometimes misunderstood implications. Dave brings up valid situations with real deadlines (e.g., seasonal deliveries, regulations) and we weigh-in on ways to handle them with or without estimates that are less likely to lead to self-sabotage. We also discuss the impact of automation on estimates, and what terms like "estimate" really mean. Continuous Delivery (CD) also takes center stage as we discuss examples of how it and the practice of "don't sell what you don't already have built" fosters trust and reduces uncertainty. We touch on the various unknowns that can arise in development, how CD can help mitigate them, and whether teams can benefit from an "#OptionalEstimates" mindset. Throughout, Dave provides practical advice on aligning practices with business goals and managing risks effectively. ### Coaching, Coding, and Higher-Level Roles Finally, we explore Dave’s thoughts on balancing hands-on coding with coaching responsibilities, especially in higher-level roles. How do you set expectations for coaches, and how can team composition shape the effectiveness of good practices? Whether you’re actively writing code or stepping back to guide others, Dave shares examples for making both approaches work. Don’t miss this episode packed with deep dives into agile practices, team dynamics, and nuanced leadership. Be sure to subscribe to the Mob Mentality Show on your favorite platform to catch this episode and others like it! Video and Show Notes: https://youtu.be/IPFYe_oOFtI…

The Mob Mentality Show

1
Impact of Teaming from a Management Perspective with Rickard Westman 43:09

cách đây 32 weeks trước43:09

43:09

In this episode of the Mob Mentality Show, we explore the profound impact of mob programming from a management perspective with our special guest, Rickard Westman. With a diverse background in sports and news software products, Rickard transitioned from a traditional solo work environment to embracing mobbing—a journey that radically transformed how teams communicate, collaborate, and deliver value. Rickard opens up about his early experiences in the industry, where he witnessed the drawbacks of isolated work patterns—particularly the delays and inefficiencies caused by waiting on pull requests. His initial encounter with mob programming was anything but smooth. The concept felt awkward and unnatural, but after Woody Zuill’s workshops and after experimenting with mobbing, Rickard and his teams discovered its potential to revolutionize their workflows. In this episode, we dive into Rickard's journey from skepticism to advocacy for mob programming. He shares how mobbing helped increase production release frequency and enhance safety within his teams. By exposing communication breakdowns and dependency issues during scaling, mob programming brought to light the hidden challenges that were stalling progress. With the introduction of multiple mob teams, these issues began to dissipate as team members naturally shared knowledge and collaborated across different areas. One of the key insights Rickard offers is the importance of slack in the system, generated through effective teaming. This slack led to greater autonomy, smoother flow, and quicker resolution of bottlenecks. Rickard recounts a compelling story where a bug fix, which would have taken six weeks in the traditional setup, was resolved in just one day through mobbing. This rapid turnaround is a testament to the power of collective problem-solving and the deep, holistic understanding of the product that mobbing fosters among team members. Rickard also touches on the shift in management responsibilities as a result of mob programming. With teams becoming more self-organizing, managers found themselves spending less time overseeing individual tasks and more time empowering their teams to make decisions. This distributed decision-making model, contrasted with the traditional command-and-control approach, aligns with principles from the book *Turn The Ship Around.* Throughout the episode, we discuss the benefits and potential pitfalls of mob programming from a management perspective. Rickard emphasizes the importance of coaching mob members to understand their contributions, especially when not working solo. He also explores how successful mob teams can serve as models for new teams, highlighting different interaction patterns for product owners, analysts, and even sports writers. Finally, we examine the meta-level impact of mob programming at the C-suite level and how it influences broader organizational decision-making. Whether you're a manager, developer, or team member, this episode provides valuable insights into how mob programming can unlock potential, foster collaboration, and drive continuous improvement in your organization. Video and Show Notes: https://youtu.be/hLN2iCBdYac…

Chào mừng bạn đến với Player FM!

Player FM đang quét trang web để tìm các podcast chất lượng cao cho bạn thưởng thức ngay bây giờ. Đây là ứng dụng podcast tốt nhất và hoạt động trên Android, iPhone và web. Đăng ký để đồng bộ các theo dõi trên tất cả thiết bị.

Nghe hơn 500 chủ đề

12 subscribers

Tương tự như The Mob Mentality Show

TERRO Ant Killer Bait Stations T300B - Liquid Bait to Eliminate Ants - 12 Count Stations for Effective Indoor Ant Control

Amazon eGift Card - Amazon Logo (Animated)

Zevo Flying Insect Trap & Cartridge - Plug in Fly Trap & Indoor Bug Catcher for Gnats, House & Fruit Flies - Mess-Free - Use in Any Room - Uses Blue & UV Light (1 Plug in Device & 1 Cartridge)

Podcast đáng để nghe

The Mob Mentality Show « » Mob Programming Meets Neuroscience: Exploring Brainwaves and Team Dynamics with Mike Bowler

Mob Programming Meets Neuroscience: Exploring Brainwaves and Team Dynamics with Mike Bowler

Podcast đáng để nghe

Chào mừng bạn đến với Player FM!

Horizon Group USA Bluey Aqua Art - Reusable Water Reveal Activity Pages With Water Pen for No-Mess Drawing and Coloring

Fiskars Bypass Pruning Shears, 5/8-Inch Cut Capacity Garden Clippers, Gardening Scissors with Sharp, Rust Resistant Steel Blade

Goo Gone Original Liquid - 8 Ounce - Surface Safe Adhesive Remover Safely Removes Stickers Labels Decals Residue Tape Chewing Gum Grease Tar Crayon Glue

Amazon Basics Clear Thermal Laminating Plastic Paper Laminator Sheets, 9 x 11.5-Inch, 200-Pack, 3mil

Tương tự như The Mob Mentality Show

Hướng dẫn sử dụng nhanh

The Mob Mentality Show « »
Mob Programming Meets Neuroscience: Exploring Brainwaves and Team Dynamics with Mike Bowler