After the discussions on testing and design in episodes 68 and 69, I had so much I still wanted to talk about in testing, design, and teaching testing and design. So I convened a panel with previous Tech Done Right Guests Avdi Grimm, Betsy Haibel, and Penelope Phippen to help me think through all these topics. I was very happy to have all of them on the show, and I think it's a great conversation. Stay tuned until the very end for an update about the show.

Today on the show we have Sandi Metz, author of Practical Object Oriented Design in Ruby and co-author of 99 bottles of OOP. I’ve literally been trying to get Sandi as a guest since we started recording the show and I’m thrilled that we’ve finally been able to connect. We talk about OOP and TDD, maybe going down a test-driven rabbit hole for a while, and also talk about what it’s like to teach and coach about OOP and TDD. I enjoyed this talk very much and I think you will, too.

I’m very excited to have Dave Thomas and Andy Hunt on the show today. Dave and Andy are the authors of the Pragmatic Programmer, which has a 20th anniversary edition that is out now, and they are the publishers of the Pragmatic Bookshelf, where they have (full disclosure) published my books a time or two. We talk about what’s changed in the new version, what being a Pragmatic Programmer means, whether there’s still a role for tech books, and how to make automated testing pragmatic. Somehow I avoid telling the slightly embarrassing story about the bad impression I made the first time I met Dave. Enjoy.

Our guest this week is Amy Newell. Amy is the Director of Engineering at Wistia, and she gave a talk at RailsConf this year entitled “Failure, Risk, and Shame: Approaching pain and suffering at work”. We have what I hope is an uplifting conversation about failure and pain, how to recognize it, and how to skillfully manage those feelings to be more resilient, prevent additional pain, and ultimately be more satisfied with your job.

Our guest today is James Coglan. James has written an extraordinary programming book called _Building Git_. In it, he describes the inner workings of the Git source control tool by re-implementing a substantial part it in Ruby, including commits, diffs, branching, and networking. Along the way he shows not just how Git works, but also details of some of the algorithms it uses. There’s also a lot about building complex systems generally. And it has some great examples of test-driven development. James and I also talk about implementing in a high-level language like Ruby, versus a lower-level language like C. It’s a unique book, and I’ve been looking forward to talking to James about it for some time.

Today on the show, we're talking about hiring with Jennifer Tu and Zee Spencer of Cohere, Thayer Prime of Team Prime, and software consultant Matt Patterson. We talk about the entire developer hiring process from how to advertise your company to potential candidates, through coding tests and interviews, and all the way to the final decision process. It's a great conversation with a lot of different perspectives and a lot of good advice. We’d like to hear from you. What do you look for when hiring developers? Let us know at <http://techdoneright.io/56> or on Twitter at `@tech_done_right`

Today on the show we’re talking about engineering management. Allison McMillan is an engineering manager for the Atom team at GitHub. We talk about what her role is within the team, how she helps her team grow and improve, and how the management role is different from her previous developer jobs. We’d like to hear from you. What makes a great engineering manager? Let us know at `techdoneright.io/55` or on Twitter at `@tech_done_right`

On this episode, we’ve got Sam Phippen and Justin Searls back for their third round on the show. Both of them have been working on new Ruby tools to better standardize your team’s style and code formatting. We talk about why they’ve decided these tools are important, what their philosophy of coding style is, how coding style relates to the Ruby community, and how they evaluate code when given a code sample to look at. We’d like to hear from you. How does your team handle differences of opinion in code style? Let us know at `techdoneright.io/54` or on Twitter at `@tech_done_right`

What has changed in web development in the last 20 years, and what do those changes say about the next 20? I recently realized that Avdi Grimm, the head chef of Ruby Tapas, Sarah Mei, of Ruby Central and Salesforce, and I all began our professional careers within a couple of weeks of each other in August 1998. I wanted to talk to them about what’s changed and what’s stayed the same. I was curious as to whether our different career paths led to similar observations. We talk about open source, agile, dynamic languages, distributed systems and how they’ve all changed or haven’t changed the developer’s experience.

How can you learn from an engineering team's failure? Can you take the examples of how others have dealt with engineering problems to improve your team's day-to-day operations. Our guest is Nickolas Means, a software manager at Muve Health, who is fascinated by engineering failures. We talk about what you can learn from studying disasters, how to create a company culture in calm times that will works smoothly in stressful times, and how a successful engineering team communicates using stories and how they handle mistakes. Along the way, we talk about the recent incident at the Seattle Airport, the CitiCorp building in Manhattan, Three Mile Island and other engineering and team missteps. We have, I hope, a successful show about failure.

What's a good way to learn a new programming language that focuses on solving problems and not merely syntax? Katrina Owen is the creator of Exercism, a tool for getting beyond "hello world" in new programing languages. She is also the co-author of 99 Bottles of OOP, and the presenter of a number of outstanding technical talks. We start off by talking about Exercism, how it started, how it evolved and what it’s good at, and then we talk about how the process by which it evolved, and how Katrina learned to analyze the project more strategically, and how that strategic thinking has helped her in other parts of her life and career.

Presenting a technical talk can be an important part of a developer's career. In this episode, we're talking about how to perform a technical talk with Saron Yitbarek. Saron runs the CodeNewbie Podcast, and others, and organizes and coaches speakers for the Codeland Conference. Saron and I both have some thoughts and opinions about how to deliver a good technical talk. This episode has a lot of tips about how to prepare, what to do at the start of a talk, how to engage the audience, and why emoji are better for slides than videos? We'll give advice on how to give the talk that only you can give and how to get the best performance that you can.

I've been attending technical conferences for years, and I've always wondered about the hidden challenges involved in putting a conference together. In this show, four of the best conference organizers I know join me to share their secrets and stories. Marty Haught, organizer of many conferences including RubyConf and RailsConf, Jen Remsik and Jim Remsik, who organize the Madison+ family of conferences, and Leah Silber, who organizes EmberConf and RustConf. Learn about budgets, picking talks, and managing facilities and vendors.

How do common Agile practices like pair programming and retrospectives work when you have diverse teams? How can you make sure that underrepresented team members have their voices heard, and how does doing so improve the way that your team delivers software? Besty Haibel, Jennifer Tu, and Marlena Compton discuss ways in which Agile practices can better serve your team in the real world. For more discussion, be sure to check out [PearConf](https://pearconf.splashthat.com/).

Why is Smalltalk the Elizabethan English of programming languages? Why has it been so influential, and how does the programming language you use affect the way you think about programming. On this episode, Kerri Miller and I talk about programming languages and communication, and what we've learned from our most recent programming language adventures.

I'm back in the testing weeds with Sam Phippen, lead maintainer for RSpec-Rails, and Justin Searls, co-founder of Test Double and author of testdouble.js. We talk about long-running test suites: are they bad, or just misunderstood? Does parallel CI solve all testing speed problems, or just some of them? Then we move to a wider view, what does it mean to test your library as part of a larger ecosystem. And, how can we leverage coverage or CI information to make for more useful testing tools over the lifetime of a project.

Have you ever wondered what it's like to work with a software team? Perhaps you are a developer wondering what you seem like from the outside? Or maybe you are starting to work with a software team and you want to know what to expect? Cat de Merode and Matt McNamara join the show to talk about their experiences as product owners interacting with developer teams. We'll talk about what developers can do to build trust, how to work with product owners on estimates and to talk about technical topics. And they'll say what the most important things developers should know about working with their product owners.

Are you a developer that wants to create your own content and build an audience? Suzan Bond joins the show to talk about how to bet on yourself. We talk about how to be comfortable marketing, how to present yourself as a credible source for developer-focused content, and how to build and maintain an audience. It's the kind of advice you'd normally have to pay a coach for, offered for free because that's how we build our audience here at Tech Done Right.

What responsibility do developers have for the consequences of their code? Liz Abinante joins the show to talk about overlooked consequences, big and small, and what you can do if you find your self being asked to do something you think is unethical. Along the way, we talk about user data, the cloud, making career choices you are comfortable with, and why you should always go to Canadian college engineering conferences when asked.

Do you have interactions with co-workers where one or both of you get angry and defensive, and everybody ends up frustrated? Today we talk to Nadia Odunayo about "Nonviolent Communication", a way to communicate that honestly addresses issues, explaining how you feel without harming the other person, and getting everybody to the point where they feel better about the situation and have a clear path to move forward. Nadia gives examples of how she uses nonviolent communication in her day-to-day life, and she tries to coach me to improve my own skills. By focusing on communication your needs and not assuming anything about others, you can make difficult discussions less difficult.

Any profession that requires you to hit a budget and a deadline while balancing the project vision with practical logistics has a lot to say to software architects and project managers. Betsy Haibel was a professional theatrical set designer before becoming a software developer and architect, and we talk about how set design is like and not like software design. Not only do we talk about favorite shows, we also give you practical advice for designing your project.

How do people learn computing? Who learns best from traditional computer science education and who from bootcamps? How can we teach people who are not developers but who need to learn some programming to do their jobs? Jeff Casimir, the founder of Turing academy, and Georgia Tech's Mark Guzdial, one of the founders of the International Computing Education Research conference, join Noel to answer these questions and also explain why Excel is both the best and the worst thing in the world.

The Internet runs on Open Source. Open Source runs on maintainers and contributors. Is that sustainable? We talk to Nadia Eghbal about her work documenting and analyzing the Open Source ecosystem. How did we get here, and how did GitHub change Open Source? Nadia answers why Open Source makes economic sense, and discusses what can make projects more sustainable (hint: it's not just money).

How can you tell whether an agile software team is successful? Many teams use a single measure: velocity. Doc Norton, author of Escape Velocity, and Claire Podulka join the show to discuss why velocity is not a useful measure: it doesn't explain the problems with an unsuccessful team, and successful teams probably don't need it. We discuss the problems with velocity, what to use instead, and get on soapboxes for our least favorite agile anti-patterns.

Is your code the kind of cluttered house you might find on a reality TV show? Or the kind of sleek, minimalist house you might find in a architectural magazine? Neither one sounds like a place you could comfortably live. Sarah Mei joins the podcast to talk about Livable Code, what makes a codebase livable, how to negotiate tension between junior and senior developers and how Rails deals with developer happiness.

How can you get honest feedback from co-workers, even when you are their manager? How can you support your team's career growth and support them as they improve their skills? Claire Lew, the CEO of Know your Company, and Dan Hodos, Table XI's Director of Operations, join Noel to discuss why listening is the most important thing you can do when getting feedback, how specific questions can break the "fine" reflex, how sticky notes can help with career growth, and the one thing you should never do in a one-on-one meeting.

What makes a code base go bad and become "Legacy Code"? Can teams avoid writing bad code? Michael Feathers, author of _Working Effectively With Legacy Code_ joins Tech Done Right to talk about technical debt, how communication can prevent bad coding practices, why coding problems are never just about code, and what it's like to go around the world seeing the worst code messes ever written.

Sam Phippen, Justin Searls, and Noel Rappin spend this episode talking about the value of test-driven development (TDD) as well as its cost. They discuss the kinds of problems that developers are likely to have after they learn TDD and attempt to apply it to a large application. Learn why Rails is both great and terrible for automated testing, and how testing can influence the structure of your code.

We talk about the role that trust has in building teams, and how improv games can help build that trust and improve the way you deliver feedback. We are joined by guests Jessie Shternshus, founder of The Improv Effect and Mark Rickmeier, CEO of Table XI.

This week, we have Ed LaFoy, who is Table XI’s Director of Mobile Development. Table XI’s mobile team does amazing work and uses a lot of external tools for testing, interface design, code quality, and beyond. If you are a web developer and looking to get a sense of how to match parts of your developer experience, listen to this interview. If you are a mobile developer, and you are having some developer pain in those areas, listen to this interview.