January 30th, 2019 | 47 mins 16 secs
code, communication, developer
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/54or on Twitter at
May 17th, 2017 | 41 mins
code, developer, testing
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.