Feel like you’re hitting a wall with your existing software projects? You're not alone. On the Maintainable software podcast, we speak with seasoned practitione... Vedi di più
5 risultati 148
Avery Quinn - Can You Quantify the Impact?
Robby has a chat with Senior Software Engineer, Avery Quinn. Avery was previously a Senior Software Engineer at Remotion. Avery starts by sharing that she finds well-maintained software to have cohesive modules, be singularly responsible in its functions, and have just a general level of refinement over time.They will dive into the benefits of having a skeleton project that you can experiment with when weighing up different dependencies, tips for onboarding engineers to your teams, things to consider when building desktop applications, what it is like to work as a consultant, and later at a product company, the software product that Remotion is building for remote software engineers, why measuring velocity on a team can be a useful metric to track, and how her recent employer tracks and prioritizes technical debt work. Avery will also share advice for those who are struggling to get buy-in to prioritize technical debt work. Stay tuned for more!Book Recommendations:Just Enough Software Architecture By George FairbanksHelpful Links:https://remotion.com/blog/refactoring-legacy-systemsSubscribe to Maintainable on:Apple PodcastsOvercastSpotifyOr search "Maintainable" wherever you stream your podcasts.Keep up to date with the Maintainable Podcast by joining the newsletter.
Carlos Blé - Código Sostenible
Robby has a chat with Carlos Blé, the CEO of Lean Mind, an organization focused on boosting the growth of developers and teams. Carlos is a software crafter, entrepreneur, mentor, speaker, podcaster, blogger, and author of several tech books in Spanish (Diseño Ágil con TDD and Código Sostenible). He is also the Founder of Savvily, a publisher specializing in tech books. Carlos will start off by sharing the four important traits of well-maintained software and examples of what maintainable tests are. He will dive into the benefits of mutation testing and exploratory testing, why engineers should advocate for a TECHNICAL_DEBT.md file in their git repository, why software engineers should aim to reduce the technical burden for their product team, services that Lean Mind offers, his latest book, Código Sostenible, and how to be a good guest in another team's codebase. Stay tuned for that and so much more!Book Recommendations:Nonviolent Communication by Marshall RosenbergHelpful Links:Carlos on LinkedInCarlos on GithubCarlos on TwitterHis Websitehttps://leanmind.es/Subscribe to Maintainable on:Apple PodcastsOvercastSpotifyOr search "Maintainable" wherever you stream your podcasts.Keep up to date with the Maintainable Podcast by joining the newsletter.
Lena Reinhard - How Will People Get Stuff Done?
Robby has a chat with Executive and Leadership Coach, Lena Reinhard (she/her/hers). Lena is a speaker, writer, and Founder of Lena Reinhard Leadership Coaching and Consulting. Previously, Lena served as the VP of Engineering with CircleCI and TravisCI, as well as the startup Founder and CEO of The Neighbourhoodie Software GmbH.From Lena’s perspective, well-maintained software is supposed to serve a business’s goals and continuously improve not just reactively. She highlights the importance of organizations investing in their engineering team's skills. Lena will also talk about software as a team sport, strategies for managing technical debt, how technical debt is a loaded term, challenges teams have faced with micro-services, and what engineers might be encountering after teammates have been laid off. Tune in for that and so much more.Book Recommendations:Into The Planet by Jill HeinerthHelpful Links:The lettuce pact 🥬 https://twitter.com/lrnrdhttps://www.linkedin.com/in/lenareinhard/Subscribe to Maintainable on:Apple PodcastsOvercastSpotifyOr search "Maintainable" wherever you stream your podcasts.Keep up to date with the Maintainable Podcast by joining the newsletter.
Eric Normand - Grokking Simplicity
Robby has a chat with software engineer, trainer, and author of the book Grokking Simplicity, Eric Normand (he/him/his). As Eric reflects on his experience, the first thought he has of well-maintained software is that it’s like a unicorn (Something you can’t find in real life), but on a more serious note, he emphasizes that smaller code bases are easier to maintain and that the maintainability of a code base is also highly dependent on the team of engineers that are working on it.Robby and Eric will dive into the pros and cons of microservices in small organizations, why teams need to ensure they know where they're going with the future of their codebase, Eric's book - Grokking Simplicity, the differences within a functional programming language, higher-order functions, Eric’s journey toward authoring a technical book, and the value of engineers being able to get comfortable moving code around in a project without needing to ask for permission first. Tune in and enjoy!Book Recommendations:Book Recommendation: The Timeless Way of Building by Christopher W. Alexander>Helpful Links:Grokking Simplicity By Eric Normand, ManningEric's WebsiteEric on LinkedInEric on TwitterSubscribe to Maintainable on:Apple PodcastsOvercastSpotifyOr search "Maintainable" wherever you stream your podcasts.Keep up to date with the Maintainable Podcast by joining the newsletter.
Henrik Warne - There is No Software Maintenance
Robby has a chat with Henrik Warne (he/him/his), the Senior Software Engineer at Talos. In Henrik’s view of well-maintained software, he talks about the importance of code having structure early on because, without structure, code tends to inevitably drift over time toward complexity. He highlights the importance of engineers being able to not only read code when they join a project but also be able to run the code and test it.Henrik will share the details of his blog titled, "There is No Software Maintenance," where he argues that software maintenance is simply software development, and how software is better seen as a product versus a project. He will talk about why all software engineers should spend a portion of their time working on bugs, tactics engineers can use to reflect on and capture their thoughts after fixing a bug, and strategies for teams to improve software and avoid rot. Stay tuned for more and enjoy.Book Recommendations:How to Win Friends & Influence People by Dale CarnegieHelpful Links:There is No Software Maintenance By Henrik WarneHenrik's BlogHenrik on TwitterHenrik on LinkedInSubscribe to Maintainable on:Apple PodcastsOvercastSpotifyOr search "Maintainable" wherever you stream your podcasts.Keep up to date with the Maintainable Podcast by joining the newsletter.
Feel like you’re hitting a wall with your existing software projects? You're not alone. On the Maintainable software podcast, we speak with seasoned practitioners who have worked past the problems often associated with technical debt and legacy code.
In each episode, our guests will share stories and outline tangible, real-world approaches to software challenges. In turn, you'll uncover new ways of thinking about how to improve your software project's maintainability. We're in this together. Enjoy the show!