On this episode, Jesse, Mo, Keith, and Brian discuss the balance between using a search engine and asking co-workers for help. When you have a tricky problem to solve, either of these tactics will include some significant trade offs. The team explains when and how to Google to be effective in programming.

On this episode, Ben, Jesse, and Daniel discuss pair programming. With the strategy of pairing comes significant benefits to productivity, code quality, rubber ducking, and knowledge sharing. Listen in for helpful tips about tooling and managing differing team strengths and energy levels.

On this episode, Jesse, Mo, Ben, and Daniel discuss the continuous improvement topic of tech conferences. They discuss how to choose a conference, the most helpful aspects of a conference, and how to attend conferences well. Perhaps most importantly, the group explains how to take full advantage of the conference by sharing knowledge with the whole team.

On this episode, Ben, Mo, Daniel, and Jesse discuss three important questions regarding the priority of testing when writing code. Could you change your code for tests? Would you change your code for tests? Should you change your code for tests? Listen in to hear about how testing is a first-order concern in writing good code.

On this episode, Ben, Daniel, Jesse, and Brian discuss software testing. From types of tests to tooling for testing, learn how tests can help you make better software in less time with reproducible, regression-preventing tests. And finally, the debate about test-driven development is rekindled again!

On this episode, Daniel, Mo, and Jesse debug all the problems. They address making and questioning assumptions as a programmer, how to debug different types of errors, and the best tooling in various operating systems. Listen in to hear about test journals, buddy debugging, rubber ducking, and much more!

On this episode, Daniel, Stephen, Ben, and Colin go beyond engineering practices to talk about another important part of the life of the developer. We call it leadership, but it involves all kinds of soft skills as well as individual ownership of practices, products, and projects. In large part, this episode reveals our "secret sauce" in team projects.

On this episode, Daniel, Brian, Stephen, and Ben discuss cultivating healthy work culture. Our work includes not only what we do, but also how we do it. For developers, this means work is not just writing code. How do we foster a positive work culture? Listen in to find out.

On this episode, Ben, Daniel, and Stephen discuss the important and often diverse tasks of supporting people using software products. The conversation includes getting feature requests, bug reports, and questions about how best to use the product. The team even dialogues over a specific, recent feature request from a customer via Twitter. Also, what role does empathy play in customer support? Listen in to learn how we manage priorities in a customer-first product business.

On this episode, Daniel, Jesse, Mo, and Brian discuss the importance of reviewing code. What are some good tools for the code review process? How early is too early to get feedback on your code? Listen in to here answers to these questions and more. And, we introduce the "It Depends" bell on this one!