{"version":"1.0","type":"rich","provider_name":"Acast","provider_url":"https://acast.com","height":250,"width":700,"html":"<iframe src=\"https://embed.acast.com/$/65de32896569fa0017d17653/6695b54f9183e32c13b2f513?\" frameBorder=\"0\" width=\"700\" height=\"250\"></iframe>","title":"Tech Death (with Robby Russell)","description":"<p>In this episode of the Dead Code podcast, host Jared Norman interviews Robby Russell, the CEO of Planet Argon and creator of Oh My Zsh, who shares insights from his extensive experience in software development, particularly Ruby on Rails. Robby discusses the challenges of software maintenance and technical debt, emphasizing the importance of understanding and managing different types of debt within teams. He advocates for building simpler, more maintainable systems, taking ownership of the codebase, and integrating maintenance work into regular workflows through effective communication and documentation.</p><p><br></p><p><strong>Links:</strong></p><p><br></p><p><a href=\"https://www.tiktok.com/@robby.pdx\" rel=\"noopener noreferrer\" target=\"_blank\">Robby’s TikTok</a></p><p><a href=\"https://www.linkedin.com/in/robbyrussell/\" rel=\"noopener noreferrer\" target=\"_blank\">Robby’s LinkedIn</a></p><p><a href=\"https://x.com/robbyrussell\" rel=\"noopener noreferrer\" target=\"_blank\">Robby’s X</a></p><p><a href=\"https://ohmyz.sh/\" rel=\"noopener noreferrer\" target=\"_blank\">Oh My Zsh</a></p><p><a href=\"https://www.planetargon.com/\" rel=\"noopener noreferrer\" target=\"_blank\">Planet Argon</a></p><p><a href=\"https://maintainable.fm/\" rel=\"noopener noreferrer\" target=\"_blank\">Maintainable Software Podcast</a></p><p><a href=\"https://www.amazon.com/Working-Effectively-Legacy-Michael-Feathers/dp/0131177052\" rel=\"noopener noreferrer\" target=\"_blank\">Michael Feathers' book \"Working Effectively with Legacy Code\"</a></p><p><a href=\"https://medium.com/@ziobrando/from-technical-debt-to-design-integrity-48e7056b6776\" rel=\"noopener noreferrer\" target=\"_blank\">Ward Cunningham and the concept of Technical Debt</a></p><p><a href=\"https://railsconf.org/\" rel=\"noopener noreferrer\" target=\"_blank\">RailsConf</a></p><p><a href=\"https://rubyonrails.org/\" rel=\"noopener noreferrer\" target=\"_blank\">Ruby on Rails</a></p><p><a href=\"https://www.refinerycms.com/\" rel=\"noopener noreferrer\" target=\"_blank\">Refinery CMS</a></p><p><a href=\"https://solidus.io/\" rel=\"noopener noreferrer\" target=\"_blank\">Solidus </a></p><p><a href=\"https://github.com/spree/spree\" rel=\"noopener noreferrer\" target=\"_blank\">Spree</a></p><p><a href=\"https://www.amazon.com/Refactoring-Improving-Design-Existing-Code/dp/0201485672\" rel=\"noopener noreferrer\" target=\"_blank\">Martin Fowler's book \"Refactoring\"</a></p><p><a href=\"https://www.amazon.com/Philosophy-Software-Design-John-Ousterhout/dp/1732102201\" rel=\"noopener noreferrer\" target=\"_blank\">John Osterhout's book \"A Philosophy of Software Design\"</a></p><p><a href=\"https://rubyonrails.org/world/2024\" rel=\"noopener noreferrer\" target=\"_blank\">Rails World 2024</a></p><p><br></p><p><a href=\"https://hachyderm.io/@deadcode\" rel=\"noopener noreferrer\" target=\"_blank\">Dead Code on Mastodon</a></p><p><a href=\"https://twitter.com/DeadCodePod\" rel=\"noopener noreferrer\" target=\"_blank\">Dead Code on X</a></p><p><a href=\"https://supergood.social/@jared\" rel=\"noopener noreferrer\" target=\"_blank\">Jared on Mas</a><a href=\"https://ruby.social/@jardo\" rel=\"noopener noreferrer\" target=\"_blank\">todon</a></p><p><a href=\"https://ruby.social/@jardo\" rel=\"noopener noreferrer\" target=\"_blank\">Jared on X</a></p><p><br></p><p><a href=\"https://drive.google.com/file/d/1RK9xwIKgGVR79rSzyzWSwSSq_4SLaYPT/view?usp=drive_link\" rel=\"noopener noreferrer\" target=\"_blank\">Episode Transcript</a></p>","author_name":"Jared Norman"}