Podcast appearances and mentions of llewellyn falco

Ravi Ram is a software engineer specializing in .NET, Azure, and intensive, high-stakes software. He started developing in 1998 with basic websites. Moved from Classic ASP with Cart.ASP. After learning about SQL injections after a client hack, he was hired by the California Department of Justice to do that work. Ravi is completely self-taught and has contributed to countless software projects over 30 years.   Topics of Discussion: [3:24] Ravi shares his career journey, starting with web design for a neighbor, moving to classic ASP, and eventually to .NET. [5:12] TechBash is a .NET conference in Pennsylvania, emphasizing its family-friendly atmosphere and the high attendance of families. [8:00] A few of Ravi's favorite moments and sessions from TechBash. [12:57] Going through code in real-time with one of the TechBash speakers. [16:51] How approachable, diverse, and friendly TechBash is. [17:11] Ravi talks about a session on scope logging with OpenTelemetry, which impressed him with its configuration capabilities. [27:49] Why the duo loves the word “seam”! [28:07] Encouragement for first-time speakers who may be interested in TechBash.   Mentioned in this Episode: Clear Measure Way Architect Forum Software Engineer Forum Programming with Palermo — New Video Podcast! Email us at programming@palermo.net. Clear Measure, Inc. (Sponsor) .NET DevOps for Azure: A Developer's Guide to DevOps Architecture the Right Way, by Jeffrey Palermo — Available on Amazon! Jeffrey Palermo's Twitter — Follow to stay informed about future events! Ravi Ram on LinkedIn https://www.linkedin.com/in/dhali/ Sandi Metz' Rules For Developers https://thoughtbot.com/blog/sandi-metz-rules-for-developers Llewellyn Falco refactoring https://www.youtube.com/watch?v=aWiwDdx_rdoSandi  Metz' Rules For Developers https://thoughtbot.com/blog/sandi-metz-rules-for-developers Llewellyn Falco refactoring https://www.youtube.com/watch?v=aWiwDdx_rdo   Want to Learn More? Visit AzureDevOps.Show for show notes and additional episodes.

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   

Dillon Kearns turns the pages of his journey with Elm, from applying meta-learning techniques as a classical piano player & agile coach to building a full-stack Elm framework (elm-pages).Thanks to our sponsor, Logistically. Email: elmtown@logisticallyinc.com.Music by Jesse Moore.Recording date: 2023.05.04GuestDillon Kearns (https://incrementalelm.com/)Show notes[00:00:32] Introducing Dillon KearnsElm Radioincrementalelm.comdillonkearns/elm-graphql (Elm Radio episode)dillonkearns/elm-markdownelm-ts-interop (Elm Radio episode)https://html-to-elm.com/elm-pages

Mob and pair programming are meant to ease collaboration and improve communication between team members. Still, other aspects of software development can also gain something from it. This is the case for testing optimization, as well as for preserving an organization's culture and growing teams. To shed light on these topics, we interviewed Llewellyn Falco, agile coach and the creator of ApprovalTests.Like this episode? Be sure to leave a ⭐️⭐️⭐️⭐️⭐️ review on the podcast player of your choice and share it with your friends.

When it comes to remote mobbing or pairing with strangers, many challenges present themselves. If I allow a remote Anydesk session into my already setup home computer, how can I know they are not going to hack me? Does my home network have sufficient upload time for everyone to prevent significant lag? If I do git handover, how can I quickly get each person's computer installed with all the required development and mobbing tools?  Come join Chris and Austin as they discuss with two seasoned mobbers (Llewellyn Falco and Jay Bazuzi) their novel cloud solution to this problem. You not only are going to get some excellent tech tips and tricks for remote mobbing with strangers, but also some facilitation wisdom. You don't want to miss this cloud mobbing show and tell! Video and show notes: https://youtu.be/vB0rF0ElOT8 

What if there was a place where all the events and trainings were done via #MobProgramming? What if you could sign up to learn from top technologists like Llewellyn Falco, James Grenning, Ken Pugh, J. B. Rainsberger, David Bernstein, Jon Reid, Amitai Schleier, Dustin Thostenson, Skylar Watson, or Lee Barnes? Look no further since PubMob.com is here! Join Austin and Thomas in this episode of the Mob Mentality Show as they discuss PubMob with Jeff Langr and also hit exciting topics like remote tools and "#PairProgramming vs. #MobProgramming". Video and show notes: https://youtu.be/AagiPPP7zgg  

We discuss with Llewellyn Falco (https://twitter.com/llewellynfalco) about mob facilitation tips & tricks and the return on investment from mob programming. Video and show notes: https://youtu.be/uBrnlDtxRcQ 

Jurgen Appelo on Agile Toolkit, Amitai Schleier on Mob Mentality, Colleen Bordeaux on Coaching For Leaders, Scott Hanselman on Hanselminutes, and Buster Benson on Lead From The Heart. I’d love for you to email me with any comments about the show or any suggestions for podcasts I might want to feature. Email podcast@thekguy.com. And, if you haven’t done it already, don’t forget to hit the subscribe button, and if you like the show, please tell a friend or co-worker who might be interested. This episode covers the five podcast episodes I found most interesting and wanted to share links to during the two week period starting March 2, 2020. These podcast episodes may have been released much earlier, but this was the fortnight when I started sharing links to them to my social network followers. JURGEN APPELO ON AGILE TOOLKIT The Agile Toolkit podcast featured Jurgen Appelo with host Bob Payne. Jurgen says that companies go through several stages in their lifecycle and investors make investment decisions based on what stage they think a company is in. Some investors, for example, wait until a company has achieved product-market fit before investing. At first, budgets are small because the risks are higher. Then, as more evidence is accumulated and the weaker companies have failed, the remaining companies get the bigger budgets. This is called an innovation funnel. Seeing how well this works in startup funding, Jurgen started to see the benefit that this could have if adopted inside organizations. Corporations tend to invest in projects by predicting what ideas will succeed. Instead, they could create an ecosystem where all the ideas can participate and they would go through stages like a startup where they need to find product-solution fit, product-market fit, and those that make it to the end get the biggest funding. They talked about business agility and Jurgen says that it is more important to focus on innovation and you will achieve business agility as part of the package. Bob pointed out that organizations are setting up skunkworks and innovation labs but, unless they can integrate their innovations with the core business, they will end up like Xerox Parc and other companies will exploit their innovations and disrupt them. Jurgen says that this innovator’s dilemma, as described by Clayton Christensen, requires you to switch to the mindset that your products and services don’t have eternal life. This is normal for any organism, but a species can live forever. The innovator’s dilemma, he says, was solved millions of years ago in nature. We need to borrow this regeneration capability from nature and say that the innovation is not the product or service; it is the system for generating products and services. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/jurgen-appelo-startup-scaleup-screwum-lean-agile-dc-2019/id78532866?i=1000465296924 Website link: https://hwcdn.libsyn.com/p/2/d/3/2d3a6b2936031059/leanAndAgileDC2019_Jurgen_Appelo.mp3?c_id=64647230&cs_id=64647230&expiration=1582618595&hwt=2e7c8bfffbafc47eef3a10950edf34ae AMITAI SCHLEIER ON MOB MENTALITY The Mob Mentality podcast featured Amitai Schleier with hosts Chris Lucian and Austin Chadwick. As a technical Agile coach, Amitai likes to sit with programmers and program, sit with testers and test, and sit with managers and manage. He loves to put things in terms of cost and risk and one of his areas of specialty is legacy code. When Amitai tried to make a career change from being a developer to being a technical Agile coach, he believed that if he could just say the right words in the right order with the right tone of voice, people would have to agree with him and behavior change would occur. This didn’t work. He realized that getting the words right is important, but you need to earn people’s trust first. He pair-coached with Llewellyn Falco and this taught him about the synergy between mobbing and coaching. One example of that synergy is in how you know whether the coaching is working. You measure by observing whether the new behaviors the coach introduced continue to be practiced when the coach isn’t around. An expensive way to test this is, after a year of coaching them, go away for a year and come back and see what still gets practiced. A cheaper and more Agile way is to have an iteration with a feedback cycle where you visit just long enough for the team to form a new habit and go away long enough to see if the habit sticks. Chris asked Amitai to talk about teams that he introduced to mobbing. Amitai described a team that had problems working together. Amitai had the program manager say to the team that, in the next iteration, if the team didn’t get fewer stories done, the manager would be disappointed because the team wasn’t trying hard enough to learn something. In practice, teams that start mobbing don’t slow down that much, but they need to hear that they’re allowed to. As a result of the switch to mobbing, the person who had been keeping decision-making for himself started talking people through what he knew, people who had previously been uninvolved started to engage with the problem-solving process, and the whole team was energized by it. Amitai doesn’t love that he had to force it on them the way he did and prefers to invite people to change their behavior, but sometimes, he says, you have to manufacture the willingness. Chris asked about the benefits and difficulties of mob programming with legacy code. First, Amitai said, mob programming is more extreme than Extreme Programming. If we were defining XP today, we would skip pairing and go straight to mobbing. Legacy code, or, valuable code we are afraid to change, is a kind of nexus of extremes as well. The cognitive challenges of software development are turned up all the way and mob programming is a great way to deal with these greater cognitive challenges. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/amitai-schleier-on-the-synergy-of-mobbing-and-coaching/id1485950034?i=1000463210922 Website link: https://mobmentalityshow.podbean.com/e/amitai-schleier-on-the-synergy-of-mobbing-and-coaching/ COLLEEN BORDEAUX ON COACHING FOR LEADERS The Coaching For Leaders podcast featured Colleen Bordeaux with host Dave Stachowiak. Dave started by asking about a quote from Colleen’s book, “Am I Doing This Right?” The Charles Jones quote says, “You are the same today that you’re going to be in five years except for two things: the people with whom you associate and the books you read.” Colleen says that when she looks at the people from whom she has learned the most and the people who helped her become who she is today, she finds that they all credit their success to the relationships they’ve cultivated and the books they’ve read. They spoke about the health implications of loneliness. Colleen says that our purpose and fulfillment in life and work is connected deeply to the relationships we cultivate and our ability to cultivate relationships is about being able to show up as ourselves. To Colleen, authenticity means being open to connecting with people and sharing your real experiences, who you are, and the challenges you’ve had so that it gives others permission to do the same. People are craving real human connection and we need to a better job of facilitating it. When Colleen was most lonely and isolated it was when she was in high school and her older brother became addicted to drugs, putting her family through an upheaval. Her high school and community had a culture of perfectionism and her family struggled not only with her brother’s addiction but also a fear of judgement from other people. Colleen felt she couldn’t share her feelings of loneliness with her friends or teachers because she didn’t know anyone who would receive it without judging her family. As she grew up and her family worked through it, she started to share her feelings and realized that the people in her network had their own struggles in their own families and were also afraid to share. They talked about how the negative relationships in our lives can make us into destructive thinkers rather than productive thinkers. Colleen described a time when she fell victim to this. She was insecure, negative, gossipy, super-judgmental, and someone who would get jealous or envious when she saw people around her succeeding and happy. The root cause, she says, was that she was not introspective and had no control over her own mindset. She says you have to look at yourself and consider, “Am I a net-positive in the lives of the people who I surround myself with? Am I somebody who encourages, supports, and gives positivity and light to the people around me or am I somebody who is quick to judge, quick to shut down, and somebody who struggles to nip my negative impulses in the bud?” When Colleen helped herself evolve from a crab to a magnanimous thinker, her relationships blossomed. She told a story about being on a huge project that involved constant travel and little autonomy. Instead of trying to fix the situation, she allowed her negativity to run rampant. She decided the problem was everybody else and the firm itself, so she went looking for a new job. She got an offer and she told one of her mentors. This mentor said, “Colleen, you can go ahead and take this job, but eventually you’re going to end up in the same situation. What are you going to do then?” She says that this hit her like a ton of bricks. Changing her circumstances might momentarily have distracted her, but it was her own thinking that was the real problem. Her mentor’s advice was that running away from things doesn’t move you forward. You are better off staying put, focusing on what you can control, and seeking what truly excites and energizes you to the point where you can’t stop thinking about it and you want to run towards it. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/455-how-to-create-great-relationships-colleen-bordeaux/id458827716?i=1000465792556 Website link: https://coachingforleaders.com/podcast/great-relationships-colleen-bordeaux/ SCOTT HANSELMAN ON HANSELMINUTES The Hanselminutes podcast featured Scott Hanselman with host Jeff Fritz. For the first time in about 700 episodes, Scott Hanselman was the guest on Hanselminutes. This episode came from an interview he did with the Live Coders who write code live in front of an audience on Twitch. Jeff asked first about Scott’s longevity. Scott’s blog has been going on for seventeen years and the podcast has been going on for fourteen years. The reason he has been able to do it consistently for that long is because he is not doing it five days a week. Scott says you need to set up systems by which your community can be self-sustaining and not require you to show up every single day. The next question came from community member roberttables. He asked how Scott delegates responsibilities for aspects of a community when community mentorship is not part of your role. Scott says that one of the things he finds communities don’t do is they don’t express what their long term goals are. He compared it to a couple getting married and having wedding vows but no mission statement. He and his wife wrote a business plan for the community of two that they were creating. When you put together a community, he says, whether it is a marriage or a community of fifty live coders, you set a tone. You have to make sure that 80 to 90% of the people are 100% behind the goals. Then, if a troll shows up, they are overwhelmed by the positivity of the group. That’s how you scale. It starts with two people agreeing on what they are doing. As an example of doing this wrong, he talked about how Reddit communities have problems because Reddit wasn’t founded with the agreement that we would all be nice to each other. Now they are trying to retcon niceness into the community. Scott says, “You can’t retcon nice.” The next question was from rockzombie2, who wanted to know how Scott grew his following. Scott says consistency is king. He asked, “How often have you visited someone’s blog and the very last blog post is a rededication of themselves to blogging?” That’s because people set up failure systems. Instead, it’s got to be something that you can’t ever stop. The interval between blog posts should be large enough that you start to miss it but not so large that coming back to it is a chore. You also need to have an internal check-in where you ask yourself, “Does this feed my spirit? Is this the thing that makes me happy?” If you feel you need a blog to grow, then that’s the wrong attitude. Michael Jolley, aka, BaldBeardedBuilder, asked how Scott manages the various kinds of content he produces. Scott says he keeps a backlog of ideas that are so good that they can write themselves. If he gets excited about something, he will both blog about it and reach out to someone related to the thing that has him excited and schedule a podcast. KymPhillpotts asked about resources for improving interviewing techniques. Scott believes interviewing is similar to improv. Just as you would in improv, you want to use the concept of “Yes, and...” He also recommended listening to early Terry Gross interviews from the mid-nineties. He recommends ignoring the content and instead studying how she conducts the interview. He says that people seem to think that you can just turn on the mic and start interviewing people and it is going to go well. He argues that you need deliberate practice. You need to listen to yourself and watch yourself on video and learn what you need to do better. Being charming is an art. You can practice it and become better at it. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/myself-its-not-weird-at-all/id117488860?i=1000462813484 Website link: https://hanselminutes.simplecast.com/episodes/myself-not-weird-at-all-HZclNwEe BUSTER BENSON ON LEAD FROM THE HEART The Lead From The Heart podcast featured Buster Benson with host Mark C. Crowley. Buster has written a book called “Why Are We Yelling? The Art Of Productive Disagreement”. Buster started out by saying that disagreements as battles has been a useful tool for us as a species before we had institutions of reason and science. It was how you claimed your spot on the hill. While “might makes right” continues to be what we fall back to when everything else falls apart, it is no longer the most productive way to think about disagreement. The kinds of problems we face today and the arena that we’re having conversations in have changed. Before, it was about keeping the tribe together. Now, it is about creating relationships and collaborating across tribes. We need to train ourselves to become great collaborators and see disagreement as an opportunity and as a skill we can practice. Mark brought up a statistic from Buster’s book that says nine in ten of us feel that arguments are almost always an unproductive venture. As a result, we steer clear of them. He asked Buster what he has learned about why having disagreements is so highly supportive of having healthy relationships. Buster says that if you think about a disagreement as a milestone or landmark of something important that is currently in a stuck state and ask what, long term, is going to best guarantee the success of this relationship, it is about becoming high-functioning in terms of addressing and facing problems and resolving them. This is difficult because avoidance is natural. When you are thrown into an arena where you don’t have the skills to operate in it successfully, you naturally run away.  Buster talked about anxiety debt. These are the things you have not been able to face with confidence and they end up wearing you down, decreasing your happiness, and making you less healthy. Just as there is never an urgent need to clean up tech debt until it threatens the success of your company, anxiety debt in your relationships can be neglected and become harder and harder to address as it accumulates over time. Mark asked how to get yourself centered so that you can have a disagreement that doesn’t knock you off your foundation. Buster says the first step is get over the misconception that we can change minds. Minds do change, but we don’t change them directly; we change them with our own mind changing. Rather than thinking “I’m going to move your mind from point A to point B”, think of your own mind and the other party’s mind each as a pile of rocks and you each have to contribute your rocks to building a new, third pile that incorporates both perspectives. This third perspective is more inclusive and transcends the problem. You don’t know in advance where the third perspective is and you have to use the other person’s perspective to triangulate it with your own. That means you have to use them as a resource rather than a receptacle of new information. Mark asked about emotional situations where things are so polarized that each side thinks the other is crazy. Buster says that in these situations, the fact that we think each other is crazy raises the question, “What do I not know about you and what do you not know about me that makes us think each other is crazy?” To resolve this, you can ask questions that you don’t know the answers to. No matter what the other party says, it will give you new information and new insight into things. Mark asked for an example. Buster says that if you are with your polar opposite political opponent, you can ask a set of questions that help you understand how their beliefs arose. These questions take you out of battle stance and help you build a relationship with them. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/buster-benson-mastering-art-productive-disagreement/id1365633369?i=1000464961355 Website link: https://blubrry.com/leadfromtheheartpodcast/55513911/buster-benson-mastering-the-art-of-productive-disagreement/ LINKS Ask questions, make comments, and let your voice be heard by emailing podcast@thekguy.com. Twitter: https://twitter.com/thekguy LinkedIn: https://www.linkedin.com/in/keithmmcdonald/ Facebook: https://www.facebook.com/thekguypage Instagram: https://www.instagram.com/the_k_guy/ YouTube: https://www.youtube.com/c/TheKGuy Website:

He's back! Tech Craftsmanship Coach Llewellyn Falco shares stories of his second visit to Amway. Some of the topics he touches on in this episode are:Anti-fragile: a systemic way of implementing things so that when they break, you get stronger. More resilient. If your system is dependent on discipline, it’s broken.Safeguarding: after an issue was resolved, the team reflected on these 3 questions to help them build more resiliency for the future: What allowed us to create this situation?What made it hard for us to discover what it was?What made it hard to fix?PS: Don't start safeguarding in the middle of a crisis; wait until it's over (but not too long). Learning through documenting: As you document something, it prompts new ideas for how the thing could work. Shared, isolated, mutable and non-mutable states: the only combination to avoid is the one that everybody chooses = shared + mutable. What the team did when multi-threading threw a wrench in their testing…Continuous improvement: stop worrying about how to improve faster, worry about starting. Make improvement an everyday habit, and speed will come later.

Johanna Rothman on Programming Leadership, Thomas “Tido” Carriero on Product Love, Adam Davidson on Lead From The Heart, Josh Wills on Software Engineering Daily, and Amitai Schleier on Programming Leadership. I’d love for you to email me with any comments about the show or any suggestions for podcasts I might want to feature. Email podcast@thekguy.com. And, if you haven’t done it already, don’t forget to hit the subscribe button, and if you like the show, please tell a friend or co-worker who might be interested. This episode covers the five podcast episodes I found most interesting and wanted to share links to during the two week period starting January 20, 2020. These podcast episodes may have been released much earlier, but this was the fortnight when I started sharing links to them to my social network followers. JOHANNA ROTHMAN ON PROGRAMMING LEADERSHIP The Programming Leadership podcast featured Johanna Rothman with host Marcus Blankenship. Marcus started out by asking Johanna why it is important to think about managing ourselves. Johanna says that when we don’t manage ourselves, we don’t have the capability to manage other people. For example, if we insist on micro-managing people, they cannot grow and we prevent them from doing their best work.⁠ ⁠Marcus asked her what micromanagement has to do with managing ourselves. Johanna says that micromanagement comes from fear. You need to learn to manage yourself to manage this fear and reduce your need to micromanage. ⁠ ⁠She says the reason the first book is about managing yourself is that if you can avoid doing the things that make people feel badly, you can create an environment where people can excel.⁠ ⁠They talked about surveys and Marcus asked Johanna’s opinion on anonymous versus named survey responses. Johanna says that when you have a culture where there is a lot of blaming and micromanagement and little coaching, she would recommend an anonymous survey.⁠ ⁠Marcus talked about how technical managers often know how to do the work itself very well and he asked Johanna when this can trip us up. One way it trips us up, she says, is that people on the team don’t get a chance to practice if the manager is writing code instead of managing. Second, when you have not been in the code in a while, you do not know what it looks like anymore. ⁠ ⁠Marcus asked how managers can get time to think in today’s high time-pressure environments. Johanna says that if you are spending a lot of time in meetings, you should be looking at whether you can delegate any of those meetings to the people doing the work. This delegating is not sloughing off your responsibilities, but making sure you are not part of a team that you are not supposed to be a part of.⁠ Apple Podcasts link: https://podcasts.apple.com/ca/podcast/becoming-better-manager-means-starting-yourself-johanna/id1461916939?i=1000460138590 Website link: https://programmingleadership.podbean.com/e/becoming-a-better-manager-means-starting-with-yourself-with-johanna-rothman/ THOMAS “TIDO” CARRIERO ON PRODUCT LOVE The Product Love podcast featured Thomas “Tido” Carriero with host Eric Boduch. Tido oversees all of engineering, product, and design at Segment. Segment provides customer data infrastructure or CDI, helping companies collect, unify, and connect data about their own interactions with their customers. It gives these companies a unified view of their customer data across all channels.⁠ ⁠When he joined Segment, Tido was blown away by how robust the ecosystem was and by the attractive idea of empowering business teams, marketing teams, and product teams by installing application tracking once and being able to turn on integrations with the flick of a switch. Often, he says, a lot of business and marketing and less technical folks are blocked from doing the best job they could do because of tough integration problems that Segment solves.⁠ ⁠Segment naturally has a lot of adjacencies. They touch critical customer data and they need to decide whether to use that to empower engineering, marketing, or others. This requires being clear at the beginning of the year that they will pick two or three bets as an organization to focus on.⁠ ⁠Eric asked Tido what product leaders often do wrong. Tido says the biggest mistake product leaders make by far is not looking in the mirror and making an honest assessment of where things are. Getting attached to an idea makes it harder to give it a critical look. Often, you’re only a small pivot away from a valuable product. As the leader of an organization, he sees his job as creating a culture where failure is not just okay but celebrated. If people are getting slapped on the hand for failure, they will just get even more committed to their first ideas. Healthy teams that seriously innovate look at the data and are willing to pivot when it tells them unpleasant things.  Apple Podcasts link: https://podcasts.apple.com/ca/podcast/thomas-tido-carriero-joins-product-love-to-talk-about/id1343610309?i=1000459980786 Website link: https://www.spreaker.com/user/casted/edited-tido-joins-product-love-mp3 ADAM DAVIDSON ON LEAD FROM THE HEART The Lead From The Heart podcast featured Adam Davidson with host Mark C. Crowley. Adam Davidson is the creator of the Planet Money podcast and is staff business writer at The New Yorker. He has a new book called The Passion Economy. The theme of the book is that choosing your career used to mean choosing between work that makes your heart sing and work that pays well but disconnects you from your passions, but the new world order demands that we follow our passions and pursue work that leverages both our talents and our interests.⁠ ⁠Adam’s grandfather worked his entire career in a ball bearing factory and only made a good living by working double shifts. He believed that people who follow their passions go nowhere in life.⁠ ⁠Adam’s father was the opposite. Making money was far less important to him than following his dream of performing as a Broadway actor.⁠ ⁠These two men represent the dichotomy of having to choose financial success or your passion but not both.⁠ ⁠The people of Adam’s father’s generation and his grandfather’s generation had to choose between a life of passion and a life of financial success, but people today, Adam says, are lucky. They are lucky for the reasons that terrify us. Adam says, “All of these forces that have done so much damage to the stability of the 20th century economy also provide exactly the tools that allow us to figure out what we uniquely love and are good at and find those people, even if they’re thinly spread all over the country or all over the globe, who also crave what it is we can provide and are willing to pay for it.”⁠ ⁠Mark summed up the book as being about combining your training and expertise with a personal passion to find your own niche. According to Adam, some people take a total left turn and go into a completely different field later in their lives, but the most successful people he has met combine their passion with the skills they have previously acquired.⁠ Apple Podcasts link: https://podcasts.apple.com/ca/podcast/adam-davidson-new-rules-for-thriving-in-twenty-first/id1365633369?i=1000462188105 Website link: https://blubrry.com/leadfromtheheartpodcast/54035306/adam-davidson-the-new-rules-for-thriving-in-the-twenty-first-century/ JOSH WILLS ON SOFTWARE ENGINEERING DAILY The Software Engineering Daily podcast featured Josh Wills with host Jeff Meyerson. Josh Wills was the director of data engineering at Slack when Slack was building out a solution to scaling its data infrastructure. When the first analysts at Slack were hired, their only option was to spin up their own little databases that had cached copies of Slack’s main transactional database. Eventually, Slack hired data engineers that built systems that could scale up what an analyst could do. They built up a lot of infrastructure involving Airflow jobs producing Parquet files on S3 that were queryable through tools like Presto and it was, according to Josh, a “ghost city” for a while. All the while, the analytics team was still using the existing infrastructure of ETL jobs running on the transactional database. It wasn’t until Slack started aggressively hiring analysts, data scientists, and engineers from the Googles, Facebooks, and Twitters of the world that they had people who knew how to use the stuff Josh and his team were building. Jeff asked how the various design philosophies coming from the new hires from Google and Facebook got resolved. Josh said it got resolved by him making all the decisions. There were a million things to do, so the design direction was often the result of whoever was the first mover. If Josh had it all to do over again, he would do many things differently, but he knows that nobody would appreciate it because they would have never experienced the inferior designs. It is hard to appreciate the pain that something saved you. Most of your good decisions are invisible and taken for granted while your bad decisions cause pain and suffering forever. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/slack-data-platform-with-josh-wills/id1019576853?i=1000462100792 Website link: https://softwareengineeringdaily.com/2020/01/10/slack-data-platform-with-josh-wills/ AMITAI SCHLEIER ON PROGRAMMING LEADERSHIP The Programming Leadership podcast featured Amitai Schleier with host Marcus Blankenship. Amitai talked to Marcus about his fork of qmail called notqmail. Qmail is a Unix program for running an email server that, unfortunately, hasn’t been updated in twenty years and has a number of rough edges. Over the last twenty years, Amitai has invested time into softening qmail’s rough edges through improved package management. More recently, Amitai started thinking about getting the people who are working on their own forks of qmail to collaborate on a single fork. The first step was getting some advice. A key piece of advice came from Llewellyn Falco. Llewellyn said, “Qmail already has a lot of nice seams and interfaces. Without too much more work and risk, you could add a couple more seams so that whatever modernization is required could be done as plugins or extensions. The next problem to think about is egos. Not all ideas are going to win.” He then gave Amitai the best piece of advice: “Whatever you do, offer yourself to other programmers to get their code converted to extensions first. As to which implementation of a particular new feature is to be incorporated, that decision is not your call. Take as extensions as many implementations as people want to give and let users decide.” Marcus asked about how to influence a group of people on a project without being coercive. Amitai says that he discovered years ago that when a situation is a little confused, his default response is to seek to lower his perceived social status. Otherwise, he cannot influence the way he wants to if he’s a big shot that people are supposed to listen to. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/collaboration-and-notqmail-with-amitai-schleier/id1461916939?i=1000462047766 Website link: https://programmingleadership.podbean.com/e/collaboration-and-notqmail-with-amitai-schleier/ LINKS Ask questions, make comments, and let your voice be heard by emailing podcast@thekguy.com. Twitter: https://twitter.com/thekguy LinkedIn: https://www.linkedin.com/in/keithmmcdonald/ Facebook: https://www.facebook.com/thekguypage Instagram: https://www.instagram.com/the_k_guy/ YouTube: https://www.youtube.com/c/TheKGuy Website:

DevOps Coach Llewellyn Falco talks about improving code you don't understand, among other technical topics. Llewellyn is known for his unique coaching style, working with teams for 2 weeks at a time and getting into the technical details with them, creating a sense of safety that allows the team to practice new techniques with low risk. Given Llewellyn's area of expertise, this episode is more technical than others.This episode briefly touches on:MOB ProgrammingTesting code w/a compilerCode reviews / confidenceRefactoring a monolith legacy systemJava

Mob Programming with Chris S. Chris Spoehr, Performance Manager and Mob Programming Expert   Mob Programming Maxims The team I'm currently on has been trying mob programming for about 4 months now. Recently, I was privileged to attend the first Mob Programming Conference. At the conference, both Woody Zuill and Llewellyn Falco gave compelling keynotes. When I returned to work, my team and I wanted to get the most out of my insights and we quickly began talking about how to level up our mobbing. We came up with an idea to introduce a third designated, rotating role to our mob when it was large enough. (Our mob flexes in size from 3-6 people.) After driving, a mobster would take on the role of 'facilitator' to observe _how_ the mob was working, and coach the mob when needed. In order to define just what these collaborative ideals are, I compiled these Mob Programming Maxims from my conference notes and slides Woody and Llewellyn have posted online. There is some affinity grouping, but no importance in the ordering. The commentary under each maxim is my interpretation of the meaning and relevance of the maxim. * For an idea to go from someone’s head into the computer it must go through someone else’s hands. - Llewellyn Falco This critical mindset behind mob programming comes from Llwellyn's "Strong Style Pair Programming". Working this way forces us to communicate clearly and completely with our teammates. When we're doing this well, this communication is at an abstraction layer. It helps build a shared mental model of the code amongst everyone on the team. * Turn up the good – Woody Zuill This concept has such depth that it deserves blog posts of its own. The core idea is one of positivity: instead of potentially applying the wrong fix to the right problem or the right fix to the wrong problem, we take something we're doing well and focus on doing it even better. As we do this, a common side effect is removing base conditions that created an issue in the first place, and those issues 'fall away.' * Just try it. It’s in the doing that we learn. – Woody Zuill & Llewellyn Falco One of the strengths of the mob comes from the breadth of ideas that comes from having "all the brilliant people working on the same problem at the same time." Often we will need to discuss how to solve the next issue in front of us. When we do, we discuss it only long enough so everyone understands the different approaches we can take. We bias ourselves toward action. We stop short of debating the merits of each approach. Just code it. We see how each approach looks in code. Then, we decide on which approach to keep, or we may discover a third, better approach has emerged. * Ask for Trust – Llewellyn Falco We ask of each person in the mob that they trust we will try everyone's ideas in turn. This is especially vital in a newly formed mob where this trust hasn't been built through experience. Without this trust in place, thrashing can occur. This kind of trust is reinforced by following the "just try it" maxim. * Respect Each Other This is another way of saying we should treat each other with "kindness, consideration, and respect", as Woody and the team at Hunter agreed to do. We take the Retrospective Prime Directive to heart and assume our teammates are contributing their best. And we're also all people. Many of us developers might not consider ourselves great at soft-skills, but it doesn't take much to not be an asshole. * Respect The Code If we're working on existing code, we should apply the Retrospective Prime Directive to the code itself. It was the best code that could be written by those who wrote at the time they coded it. Even though we may know so much better now, belittling the code (and those who wrote it) doesn't move us forward. However, this doesn't mean not refactoring or rewriting the code. We do need to respect it enough to understand its intention. * Be prepared to contribute the right thing, at the right time, in the right way – Woody Zuill When we are in the mob, we should all be prepared to contribute. This may manifest through navigating or driving. It may also manifest through doing research as a navigator to look up the API documentation the mob needs. We are mobbing because we are all valuable to the work being done. We should commit our focus to that work. A key aspect of this maxim is to *resist over-contributing*. We must practice the art of not talking to allow space for others to contribute. Using the single-navigator style of mobbing, where only one team member at a time acts to navigate the driver, while the rest silently observe until their turn, helps to reinforce this skill. * Communicate so the driver understands * Intent * Location * Instruction As navigators, we want to communicate with our driver at the highest possible level of abstraction. We want to start by communicating the intent of what should be done next, "we need to call the backend to get a list of possible widgets." Only if the driver needs further explanation do we drop down to location, "On line 123 we have a service object that we can call." Lastly, we may sometimes need to give specific instructions to a particular driver, "On line 123, type: var widgets = service.getWidgets();." This may be needed for a new dev or even just new to the tech stack. * Once the driver understands intent, navigator(s) may move on. We trust that once our driver understands our intention, we as navigators can start talking about what's next. Getting good at working this way allows us to see the full benefits of the group's collective knowledge and collaboration. * Rotate as often as is beneficial We want to rotate often enough to keep everyone engaged in the work we're doing. We prefer shorter rotation times. In fact, the quicker the rotation time the better the mob has to be at switching. Short rotation times also encourage turning up the good on the other mob programming maxims. There is no one-size-fits-all rotation time. Through experimentation and talking to others at the Mob Programming Conference, our team has discovered that "everyone drives at least once per hour" is a fair heuristic. Our team even added to it to prefer 10 minutes or shorter rotations. * Take Breaks When mobbing its easy to not take breaks. We can get into a groove and lose track of time. Or we might think about taking a break but no one else seems to need one so we don't speak up. Part of keeping our workspace comfortable is making sure we take time to physically stretch and rest our minds. Don't be afraid to call for bio breaks. I hope having these Mob Programming Maxims consolidated in one place helps your mobbing. I look forward to continuing this conversation as we discover more about this new way of working.

Richard Kasperowski Interviews Llewellyn Falco. Llewellyn is a technical coach specialized in rapid mob programming and in building remote teams. Llewellyn and I chat about the ways of growing, rather than engineering, successful teams. Llewellyn shares with us his insights about the importance of team chemistry, the ever-evolving team dynamics, and the paramount value of happiness at work. Connect with Llewellyn on Twitter at https://twitter.com/LlewellynFalco and check out his blog at http://llewellynfalco.blogspot.com/. Read the full transcript at https://kasperowski.com/podcast-25-llewellyn-falco/.

In this episode we discuss Mob Programming, a style of programming in which the entire team sits together and works on a single task at a time. Our guest, Llewellyn Falco, is one of the thought leaders on this technique – he explains how Mob Programming helps teams learn and how it accelerates the delivery of working software. The episode is full of insights and practical advice for engineering managers, agile coaches and team members. Links: https://twitter.com/llewellynfalco?lang=en http://llewellynfalco.blogspot.com/ https://www.linkedin.com/in/llewellynfalco http://www.mobprogrammingguidebook.com/ Email: llewellyn.falco@gmail.com

Llevellyn took us way back to the point where he discovered his first computer and FORTRAN. We brushed over his studies and drifted toward MobProgramming after talking about dancing. Llewellyn told us about how he discovered "strong style pair programming" and how it brought the joy of programming back in his life.Llewellyn Falco is an independent agile coach who spends most of his time programming in Java and C# specializing in improving legacy code. He is creator of the open source testing tool ApprovalTests, he discovered strong-style pair programming, he is the co-founder of TeachingKidsProgramming.org and finally co-author of the "Mob Programming Guidebook".Here are the links of the show:https://twitter.com/llewellynfalcohttps://llewellynfalco.blogspot.com/p/sparrow-decks.htmlhttp://teachingkidsprogramming.orgCreditsMusic Aye by Yung Kartz is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 License.Your hostSoftware Developer‘s Journey is hosted and produced by Timothée (Tim) Bourguignon, a crazy frenchman living in Germany who dedicated his life to helping others learn & grow. More about him at timbourguignon.fr.Want to be next?Do you know anyone who should be on the podcast? Do you want to be next? Drop me a line: info@devjourney.info or via Twitter @timothep.Gift the podcast a ratingPlease do me and your fellow listeners a favor by spreading the good word about this podcast. And please leave a rating (excellent of course) on the major podcasting platforms, this is the best way to increase the visibility of the podcast:Apple PodcastsStitcherGoogle PlayThanks!Support the show (http://bit.ly/2yBfySB)

Rob and Jason are joined by Clare Macrae to discuss Approval Tests and how they can be used to quickly test legacy C++ code.   Clare is an independent consultant, helping teams streamline their work with legacy and hard-to-test C++ and Qt code. She has worked in software development for over 30 years, and in C++ for 20 years. Since 2017, she has used her spare time to work remotely with Llewellyn Falco on ApprovalTests.cpp, to radically simplify testing of legacy code. She has enjoyed this so much that she recently went independent, to focus even more on helping others to work more easily with legacy code.      Clare was until recently a Principal Scientific Software Engineer at Cambridge Crystallographic Data Centre. She is the original author of their popular 3D crystal structure visualisation program Mercury. News Cmake 3.15 available Clang/LLVM Support for MSBuild Projects LEAF light-weight error-handling lib seeking Boost review manager Clare Macrae @ClareMacraeUK Clare Macrae's Blog Links C++ Approval Tests Approval Tests #include Happy one-of-our-birthdays #include! Sponsoring Diverse CppCon 2019 Attendees #include sponsorship for CppCon 2019 Sponsors Errors that static code analysis does not find because it is not used PVS-Studio in the Clouds - Running the Analysis on Travis CI Hosts @robwirving @lefticus      

01:32 - Clare’s Superpower: Collecting and Sharing Useful Information 04:31 - Llewellyn’s Superpower: The Ability to Collaborate with Others 08:01 - Pairing Together: C++ Version of ApprovalTests (https://github.com/approvals/ApprovalTests.cpp) 12:15 - Pairing Retrospectives: What emotions did you feel? MindMup (https://www.mindmup.com/) 16:21 - Kinship Formed Through Working Together 18:55 - Working Asynchronously vs Live Pairing 20:15 - Writing Documentation for Pairing Sessions and Working to Improve the C++ Community Culture #include (https://www.includecpp.org/) 30:44 - Safeguarding: Harnessing Pain For Good Safeguarding: A step-by-step guide (http://llewellynfalco.blogspot.com/2018/12/safeguarding-step-by-step-guide.html) MarkdownSnippets (https://github.com/simonCropp/MarkdownSnippets) 35:04 - Documentation Cont’d Turning “Error Messages” Into “Help Messages” Healthy Abstractions Testing Communication 45:08 - Asking “Why” Questions vs “What” Questions: Observability Reflections: John: The idea of using a retrospective in such a small scale. Also, the difference in the level of community while pairing: building kinship. Clare: Read more about the paradigm framing effect. Llewellyn: Being appreciative of the people you pair with. Arty: Taking the time to think about what you’re doing from the perspective of sharing affects what you do. This episode was brought to you by @therubyrep (https://twitter.com/therubyrep) of DevReps, LLC (http://www.devreps.com/). To pledge your support and to join our awesome Slack community, visit patreon.com/greaterthancode (https://www.patreon.com/greaterthancode) To make a one-time donation so that we can continue to bring you more content and transcripts like this, please do so at paypal.me/devreps (https://www.paypal.me/devreps). You will also get an invitation to our Slack community this way as well. Amazon links may be affiliate links, which means you’re supporting the show when you purchase our recommendations. Thanks! Special Guests: Clare Macrae and Llewellyn Falco.

Fredrik talks to Woody Zuill, writer of the book on mob programming, facilitator of happy teams and thoughtful teller of stories. Woody talks about how he and his team discovered mob programming, how it is evolving, how focusing on the good is the way forward, and how he may have aquired his mindset. Recorded on-stage at Øredev 2018. Thank you Cloudnet for sponsoring our VPS! Comments, questions or tips? We are @kodsnack, @tobiashieta, @oferlund and @bjoreman on Twitter, have a page on Facebook and can be emailed at info@kodsnack.se if you want to write longer. We read everything we receive. If you enjoy Kodsnack we would love a review in iTunes! Links Øredev 2018 Woody Zuill Mob programming Turn up the good - Woody’s presentation at Øredev 2018 No estimates Test-driven development Hunter industries Llewellyn Falco Pair programming Agile alliance George Dinwddie Ron Jeffries Repenning, N. and J. Sterman: Nobody ever gets credit for solving problems that didn’t happen Horticulture Titles I think of myself as a software developer Trying to make a better work environment I don’t believe we can manage people This time of year seven years ago Purely by accident Sitting and thinking at the keyboard alone One member who’s not there Five or six people programming Opening different doors If you open a door, there’s a good chance somebody will welcome you in Superconnectors One of those connector things Oddly, it is working for us Purposeful stumbling I stopped looking for solutions to problems A habit we need to build I just went ahead and did it I’ll discover stuff if I just try it We follow the path that develops in front of us Your job is very important He was extending trust to me These things are not related A gentle way to think about our lives

This week on the NFJS podcast I'm joined again by LLewellyn Falco where we discuss Mob Programming. Mob programming is a software development approach where the whole team works on the same thing, at the same time, in the same space, and at the same computer. This is similar to pair programming where two people sit at the same computer and collaborate on the same code at the same time. With Mob Programming the collaboration is extended to everyone on the team, while still using a single computer for writing the code and inputting it into the code base. What are the strategies that make this more or less successful? How can we experiment with this in our team, Llewellyn gives us insights on this and more.

We all have to deal with legacy code. As frustrating as legacy code can be, legacy code is important. Legacy code has users. Legacy code is in the wild delivering value making people's life's better. It must evolve, it must be maintained so how do we manage best this? How do we improve this codebase consistently, reliably, and safely?  This week I'm joined by LLewellyn Falco, Agile Coach, Creator of ApprovalTests, Co-Founder of TeachingKids Programming, and Legacy Code Expert.

This month on the Cucumber Podcast we speak to Beth Skurrie, who is the maintainer of the open-source project, Pact. Pact falls into the category of contract testing and with the advent of microservices and continuous delivery, it's getting more and more important. Seb Rose takes the hosting duties with extra questions from Steve Tooke. Shownotes: Learn more about Pact - https://docs.pact.io/ Integration Tests are a Scam by JB Rainsberger - http://blog.thecodewhisperer.com/permalink/integrated-tests-are-a-scam What is Pact good for? What is Pact not good for? https://docs.pact.io/documentation/what_is_pact_good_for.html Previous podcast about Approval Testing w/ Llewellyn Falco https://cucumber.io/blog/2017/01/26/approval-testing

In this special episode, returning guest, speaker and Agile technical coach Llewellyn Falco co-hosts with Corgibytes’ Chief Code Whisperer M. Scott Ford. They recap the talks they attended and cover topics such as pitching talks, the value of meetups and practice, adapting talks on-the-fly, pair programming, how technical “debt” is like credit card debt and weight gain, and more.

Llewellyn Falco (@llewellynfalco) and Amitai Schleier (@schmonz) joined me (@RyanRipley) to discuss Agile Coaching, types of coaching, hiring coaches, and some #MobProgramming. [featured-image single_newwindow=”false”]Llewellyn Falco[/featured-image] Llewellyn is a professional teacher, speaker, agile programmer, and creator of the Approval Test project. He blogs here, appears on podcasts there, and helps make agile teams awesome everywhere. Llewellyn generously shares his insights on YouTube. Watch his videos, they are great. Seriously. Amitai is a software development coach, speaker, legacy code wrestler, non-award-winning musician, award winning bad poet, and the creator of the Agile in 3 Minutes podcast. He blogs at schmonz.com and is a frequent guest on Agile for Humans. Amitai has published many of his agile observations and musings in his new book – Agile in 3 Minutes on Lean Pub. In this episode you'll discover: How to hire an agile coach Different ways agile coaches work with teams Why you may want to get out to Boston on April 6th and 7th for the Mob Programming Conference Links from the show: Mob Programming Conference Agile in 3 Minutes #32 – Mob by Amitai Schleier The Beer Game AFH Episode 27 on #MobProgramming with Woody Zuill [callout]Written in a fast-paced thriller style, The Goal, a gripping novel, is transforming management thinking throughout the world. It is a book to recommend to your friends in industry – even to your bosses – but not to your competitors. Alex Rogo is a harried plant manager working ever more desperately to try improve performance. His factory is rapidly heading for disaster. So is his marriage. He has ninety days to save his plant – or it will be closed by corporate HQ, with hundreds of job losses. It takes a chance meeting with a professor from student days – Jonah – to help him break out of conventional ways of thinking to see what needs to be done. Click here to purchase on Amazon.[/callout] [reminder]What are your thoughts about this episode? Please leave them in the comments section below.[/reminder] Want to hear another podcast about the life of an agile coach? — Listen to my conversation with Zach Bonaker, Diane Zajac-Woodie, and Amitai Schlair on episode 39. We discuss growing an agile practice and how coaches help create the environments where agile ideas can flourish. One tiny favor.  — Please take 30 seconds now and leave a review on iTunes. This helps others learn about the show and grows our audience. It will help the show tremendously, including my ability to bring on more great guests for all of us to learn from. Thanks! This podcast is brought to you by Audible. I have used Audible for years, and I love audio books. I have three to recommend: Agile and Lean Program Management by Johanna Rothman Scrum: The Art of Doing Twice the Work in Half the Time by Jeff Sutherland The Lean Startup by Eric Ries All you need to do to get your free 30-day Audible trial is go to Audibletrial.com/agile. Choose one of the above books, or choose between more than 180,000 audio programs. It's that easy. Go to Audibletrial.com/agile and get started today. Enjoy! The post AFH 058: Agile Coaching Strategies with Llewellyn Falco [PODCAST] appeared first on Ryan Ripley.See omnystudio.com/listener for privacy information.

This month on the Cucumber podcast we speak to Llewellyn Falco. He's best known for two things: approval testing and mob programming. As we've covered mobbing in great detail on the pod lately, we dig into approval testing. A very informative and fun pod. From the Cucumber team on the podcast are Steve Tooke, Aslak Hellesoy, and Seb Rose. You say hello to Llewellyn on Twitter - https://twitter.com/LlewellynFalco Or read more: http://approvaltests.com/ http://llewellynfalco.blogspot.de/ Please share and subscribe to our podcast. It truly makes us happy. Say hello to us on Twitter https://twitter.com/cucumberbdd

We sit down with Llewellyn Falco at Agile Open California following his amazing talk at Agile Games West. Llewellyn tells us about growing up a gamer and what he looks for in a game when coaching and teaching. Be sure to check him out at a conference near you! http://llewellynfalco.blogspot.com/ @LlewellynFalco Your hosts Paul and Laura http://agilegameswest.com/ http://agilegamespodcast.com/ @WorkAgile http://www.workagileconsulting.com/ @LauraPowers http://poweredbyteams.com/

Maaret Pyhäjärvi is a tester and Llewellyn Falco is a developer, and they have been pair-programming wrong... or have they? They call it strong-style pairing. It's common in pairing for the one with the idea to drive, grabbing the keyboard and running with their idea. In other words, the person with the idea is the driver, while their pair is the navigator. But if you don't know where the driver is going, you can't navigate. Strong-style is kind of a role reversal where the person with the idea lets their pair drive and instead takes on the navigator role. This way both people in the pair actively contribute. The problem with the traditional driver-navigator model is that the "navigator" doesn't have anything to do if the driver is also the ideator. The navigator can get bored or disengaged. What's more is that strong-style pairing can help pairs build trust more quickly and to help each other with new dev tricks and techniques. This concept can also be used in Mob Programming. John Esposito, Editor-in-Chief of DZone, SolutionsIQ partner, hosts at Agile2016 in Atlanta, GA. About Agile Amped The Agile Amped podcast series connects the community through compelling stories, passionate people, shared knowledge, and innovative ideas. Fueled by inspiring conversations with industry thoughtleaders, Agile Amped offers valuable content – anytime, anywhere. To receive real-time updates, subscribe at YouTube, iTunes or SolutionsIQ.com. Subscribe: http://bit.ly/SIQYouTube, http://bit.ly/SIQiTunes, http://www.solutionsiq.com/agile-amped/ Follow: http://bit.ly/SIQTwitter  Like: http://bit.ly/SIQFacebook

Llewellyn Falco is a technical coach and the creator of Approval Tests. In this episode, we go into how using Approval Tests can help your team communicate better and work on fragile codebases with confidence. 

In this week's podcast Richard Seroter talks to James Shore, author of The Art of Agile Development and one of the original signatories of the Agile Manifesto. Also on the podcast are Llewellyn Falco, creator of the open source testing tool ApprovalTests and co-founder of Teaching Kids Programming, and Rebecca Wirfs-Brock, inventor of Responsibility-Driven Design, as well as the author of books including Designing Object: Oriented Software and Object Design: Roles, Responsibilities and Collaborations. Why listen to this podcast: - A lot of people know how to do TDD and refactoring for the back end, but not for the font, but the basics are the same. - The basics of Test-Driven Development are the same for the front or back end. - If you don't know what's wrong, you don't know how to fix it. - The most common code smells, according to Llewellyn Falco: Clutter, long lines, long methods, duplication, and inconsistency. - How do we make, in an agile way, the architectural work visible, and not ignore it? - How do you have an incremental architecture and get measurements? If I say to you I'm going to go away for six months and figure it out, that's not very measurable. Notes and links can be found on InfoQ: http://bit.ly/1Pse2r1 1m:10s - The talk 'Agile Engineering for the Web' was about how do you bring typical Agile engineering ideas like TDD and refactoring to the front-end languages. 1m:33s - A lot of people know how to do these things on the back-end, but when you get to the front end a lot of people just throw up their hands. 2m:24s - I see CSS bugs all the time, because it's very hard to refactor CSS without breaking something. Quick scan our curated show notes on InfoQ. http://bit.ly/1Pse2r1 You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. http://bit.ly/24x3IVq

Hosts Ryan Ripley, Amitai Schlair, Woody Zuill Discussion Ryan Ripley (@ryanripley), Amitai Schlair (@schmonz) and Woody Zuill (@WoodyZuill) got together to discuss Mob Programming (#MobProgramming). Mob programming involves the whole team working on the same thing, at the same time, in the same space, and at the same computer. You can think of it as pair programming turned up to eleven. We talked about the benefits that mob programming can bring to a team, how it can simplify the hiring and on-boarding process, and what to do when the mob needs some alone time. We have to pay attention to what’s working and continually turn up the good!Tweet This We also learned about the Mob Programming Conference coming to Cambridge, Mass on May 1st and 2nd. Hosted by Agile New England and organized by Nancy Van Schooenderwoert, Llewellyn Falco, Woody Zuill, Kurt Kilpela, and Peter Carmichael this is shaping up to be the event to attend if you are interested in learning about and seeing Mob Programming in action. And then…we called it a night. Will you help the Agile for Humans podcast grow? Please review Agile for Humans on iTunes and leave your comments on the blog site. Help your friends and co-workers find Agile for Humans by sharing your favorite episodes with them. Thanks for all you do to support the show. Agile for Humans is brought to you by audible.com – get one FREE audiobook download and 30 day free trial at http://www.audibletrial.com/agile Resources, Plugs, and More Ryan – https://ryanripley.com AgileIndy 2016 – April 12 in Indianapolis, IN Path to Agility Conference – May 25 & 26 in Columbus, OH Amitai – http://www.schmonz.com/ Agile in 3 Minutes on LeanPub.com Agile in 3 Minutes Episode #32 – Mob How to Develop Humans Mr. Bunny’s Big Cup o’ Java by Carlton Egremont III Woody – http://zuill.us/WoodyZuill/ Beyond Legacy Code by David Scott Bernstein Mob Programming Conference – May 1 & 2 in Cambridge, MA The post AFH 027: Mob Programming with Woody Zuill [PODCAST] appeared first on Ryan Ripley.See omnystudio.com/listener for privacy information.

Guest: Llewellyn Falco @LlewellynFalco Full show notes are at https://developeronfire.com/podcast/episode-067-llewellyn-falco-must-ship-it

What are the habits that make a successful developer? Carl and Richard talk with Llewellyn Falco about the ongoing process of being the best developer you can be. Llewellyn discusses his role as a consultant to different organizations, and how often he discovers that there are simple practices just not happening within a team that would make everyone more effective. How do you create change in that scenario? How many times do you have to repeat a new approach to things before it actually sticks? Lots of psychology to actually gathering the habits that will make you the best developer you can be!Support this podcast at — https://redcircle.com/net-rocks/donations

What are the habits that make a successful developer? Carl and Richard talk with Llewellyn Falco about the ongoing process of being the best developer you can be. Llewellyn discusses his role as a consultant to different organizations, and how often he discovers that there are simple practices just not happening within a team that would make everyone more effective. How do you create change in that scenario? How many times do you have to repeat a new approach to things before it actually sticks? Lots of psychology to actually gathering the habits that will make you the best developer you can be!Support this podcast at — https://redcircle.com/net-rocks/donations

Llewellyn Falco is an Instructor for DevelopMentor. He is an  international speaker and the creator of the open source testing tool ApprovalTests ( www.approvaltests.com ). He spends most of his time programing in Java and C#. He also volunteers creating courseware and teaching kids to program ( www.teachingkidsprogramming.org ). Find his blog at llewellynfalco.blogspot.com Llewellyn is the son of a university professor, and game designer ( Set, Quiddler ) his first family computer was a Dec PDP11 mainframe, which he started programming Fortran on at age 11. Linkedin: http://www.linkedin.com/profile/view?id=1828806 Twitter: @llewellynfalco Resources: http://bit.ly/18IVPdF Please thank our sponsors @StartupProduct@AIPMM@Sprintly   

Carl and Richard talk to Lynn Langit and Llewellyn Falco about how developers can teach their kids to program. While Lynn and Llewellyn have been teaching all sorts of kids how to program (check out the links below), they've recently published a Pluralsight course specifically for developers to teach their own kids how to program. The course is completely free - you don't need to sign up for anything! And the course lets you as a developer work with your children step by step to learn how to develop in Visual Studio - yes, with your own tools. Want to show your children what you do for a living? Take it out for a spin!Support this podcast at — https://redcircle.com/net-rocks/donations

Scott is at the Agile Open Northwest open spaces conference with Llewellyn Falco this week. He talks to Llewellyn about his "Approval Tests" open source project. It's a polyglot framework to make test verification much easier when Assert() isn't enough.

Derek Neighbors: Hello! Welcome to another episode of the scrum‑cast, I'm Derek Neighbors.

With Rspec and Cucumber, Ruby has brought testing to a whole new level, but tests still require a lot of work. But things just got better. Llewellyn Falco will show you new patterns and practices to dramatically decrease the amount of effort needed to test.

Llewellyn Falco and Lynn Langit talk about their free curriculum for teaching kids programming, involving Microsoft SmallBasic.Support this podcast at — https://redcircle.com/net-rocks/donations

Carl and Richard talk to Lynn Langit and Llewellyn Falco about how developers can teach their kids to program. While Lynn and Llewellyn have been teaching all sorts of kids how to program (check out the links below), they've recently published a Pluralsight course specifically for developers to teach their own kids how to program. The course is completely free - you don't need to sign up for anything! And the course lets you as a developer work with your children step by step to learn how to develop in Visual Studio - yes, with your own tools. Want to show your children what you do for a living? Take it out for a spin!Support this podcast at — https://redcircle.com/net-rocks/donations