How to ensure that your code review practices are not just an expensive bottleneck in your team’s productivity but its ultimate superpower? Today we talk with Michaela Greiler, a Head of Research at DX and the owner of a consultancy and training company, Awesome Code Reviews, focused on helping development teams improv

Common Lisp was written in the 80s as a kind of an amalgam of the existing Lisps at the time. To make sure the Common Lisp would stay relevant, it was made backward compatible so that existing legacy systems could run on it. One thing in common to these big old systems like Lisp is a lot more mutation, and the cool thi

Ruby on Rails is a fast-moving community and it is not always easy to keep up with it. Given the efficiency of the framework, however, it is well worth trying. Today we talk to Robby Russell, creator of Oh My Z Shell, host of Maintainable software podcast, and CEO of Planet Argon – a software consultancy that helps org

In the last episode of 2020, we took a stroll through the little known corridors of coding history with Clive Thompson. Clive is a technology and science journalist for the New York Times Magazine, Wired, Smithsonian, and many other outlets. In his new book Coders: The Making of a New Tribe and the Remaking of the Worl

As menders working with legacy code, we are focused on identifying and reducing technical debt. But how much easier this task would be if the creator of the code or the previous maintainer left us some breadcrumbs to follow? A simple note on the rationale for a particular decision they have made or a warning about inte

Robby speaks with M. Scott Ford, CTO and Chief Code Whisperer at Corgibytes and co-host of the Legacy Code Rocks podcast. They discuss the difference between Makers and Menders, how to prioritize a technical debt backlog, and how to provide feedback to other developers.Helpful LinksM. Scott Ford on TwitterCorgibytesLeg