Robby has a chat with Noah Clark, a consulting applications developer at Merchants Bonding Company, one the top 15 largest surety writers in the United States. On the top of Noah’s list of things that facilitate the maintainability of software is team dynamics. Well-maintained software can never be achieved by a single individual refactoring code or having grand ideas/visions. It’s not made possible by a team coming together and committing to a practice of well-maintained software. He highlights trust and communication between a team and the company they’re developing software for as key. He also advises engineers to avoid writing code just to solve problems.Tune in as Robby and Noah discuss why engineers should ensure that their software code leans on the business domain especially when it comes to naming things, how teams can determine when it’s necessary to refactor and/or improve existing software, the complexities that come with basing software development projects on best practices, why and how to avoid blog post driven development, why referring to "organizational debt" might be more effective than "technical debt", and so much more. Enjoy!Book Recommendations:The 5 Love Languages by Gary Chapman - https://5lovelanguages.com/I Will Teach You to Be Rich by Ramit Sethi -  https://www.iwillteachyoutoberich.com/Helpful Links:https://www.linkedin.com/in/noahmclark/https://twitter.com/nolarknoahSubscribe to Maintainable on:Apple PodcastsOvercastSpotifyOr search "Maintainable" wherever you stream your podcasts.Join the discussion in the Maintainable Discord Community