The mere fact that any particular legacy code is still in use is a testament of its sustainability. Today we talk with Dr. Carola Lilienthal, the CEO of the Workplace Solutions and the author of Sustainable Software Architecture about the importance of a good structure for the durability of a software. Building upon her experience dissecting more than 300 software systems of various sizes, Carola shares with us her philosophy, methodology, tools and criteria for assessing the sustainability of a system and explains how to structure any software around its fundamental building blocks in order to achieve its durability.
The idea of a “lone genius” unleashing software marvels on the world is mostly a myth. Almost all good software is a product of the exchange of ideas, continuous discussions, and collaborations. Today we talk with Coraline Ada Ehmke - the creator of the Contributor Covenant and the laureate of the Ruby Hero Award - about the importance of kindness and empathy in coding. From creating safe spaces for discussions and exchange of ideas, through introducing empathy into understanding user needs and collaborators’ concerns, to creating a kinder programming language and the code itself - Coraline shares her thoughts with us on the whys and hows of kindness in software industry. When you are done with the episode, make sure to visit Coraline’s web-site.
Technical debt is just like a financial debt - incurring it responsibly boosts the development and growth, but failing to repay it in time can lead to bankruptcy and complete failure of the program. Today we talk with Tim Doherty, Staff Software Engineer at Procore Technologies and a co-organizer of the Santa Barbara JavaScript Meetup, about the responsible management of technical debt. Tim breaks down for us the Ward Cunningham’s definition of technical debt into sub-categories and shares with us the justifications for the acquisition and strategies for prudent repayment of these diverse kinds of technical debt. When you are done with the episode, you can check out Tim’s blog post that steered our conversation.