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 Recommendation: The Timeless Way of Building by Christopher W. Alexander>

• Grokking Simplicity By Eric Normand, Manning
• Eric's Website
• Eric on LinkedIn
• Eric on Twitter

Subscribe to Maintainable on:

• Apple Podcasts
• Overcast
• Spotify

Or search "Maintainable" wherever you stream your podcasts.

Keep up to date with the Maintainable Podcast by joining the newsletter.

Subscribe to Maintainable on:

• Apple Podcasts
• Spotify

Or search "Maintainable" wherever you stream your podcasts.

Keep up to date with the Maintainable Podcast by joining the newsletter.

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.

• How to Win Friends & Influence People by Dale Carnegie

• There is No Software Maintenance By Henrik Warne
• Henrik's Blog
• Henrik on Twitter
• Henrik on LinkedIn

Subscribe to Maintainable on:

• Apple Podcasts
• Overcast
• Spotify

Or search "Maintainable" wherever you stream your podcasts.

Keep up to date with the Maintainable Podcast by joining the newsletter.

Subscribe to Maintainable on:

• Apple Podcasts
• Spotify

Or search "Maintainable" wherever you stream your podcasts.

Keep up to date with the Maintainable Podcast by joining the newsletter.

Robby has a chat with Andy Croll (he/him/his), the CTO at CoverageBook, a Rubyist, the Organizer of the Brighton Ruby Conference, an author, speaker, and bootstrapper. The most important thing when it comes to the maintainability of software is “That code is read much more than it’s written”, Andy says. He insists that the core focus should always be on readability. 

Andy will dive into the rationale for why weird things in our code should stay weird until we find a better way to express it and even shared some specific examples within a Ruby on Rails environment. He will share his career journey from the front end into the backend, what prompted him to start the First Ruby Friend project to connect newcomers to a community with people who want to be mentors, examples of how to manage technical debt in a small team and why it's okay to let some stuff "sit in the air", and so much more. Stay tuned. It’s going to be an epic one.

• The Overstory by Richard Powers

• Andy's website
• One Ruby Thing
• Brighton Ruby
• First Ruby Friend

Subscribe to Maintainable on:

• Apple Podcasts
• Overcast
• Spotify

Or search "Maintainable" wherever you stream your podcasts.

Join the discussion in the Maintainable Discord Community

Subscribe to Maintainable on:

• Apple Podcasts
• Spotify

Or search "Maintainable" wherever you stream your podcasts.

Keep up to date with the Maintainable Podcast by joining the newsletter.

Robby has a chat with Marianne Bellotti (she/her/hers), the Engineering Manager at Rebellion Defense. Marianne is the author of the books, “Hiring Engineers” and “Kill it with Fire”. She talks about the maintainability of software being about whether software can be changed and how easily changes can be made to it. She dives into her experience with legacy modernization and talks about how to effectively judge software.

Marianne also shares her insights on the challenges teams face when people don't understand how older code works, the value of developing a plan around tests to naturally build confidence within an organization, why it's important to have a safe space to break things (e.g., staging/QA environments), how onboarding metrics can be difficult to compare when dealing with regulatory systems, and building empathy toward previous engineers on a project. Tune in for that and a whole lot more in this value-packed 61-minute episode.

• Drift into Failure: From Hunting Broken Components to Understanding Complex Systems by Sidney Dekker

• Kill it with Fire: Manage Aging Computer Systems (and Future Proof Modern Ones) by Marianne Bellotti
• Website - bellotti.tech
• https://github.com/mbellotti
• Twitter - twitter.com/bellmar

Subscribe to Maintainable on:

• Apple Podcasts
• Overcast
• Spotify

Or search "Maintainable" wherever you stream your podcasts.

Join the discussion in the Maintainable Discord Community

Subscribe to Maintainable on:

• Apple Podcasts
• Spotify

Or search "Maintainable" wherever you stream your podcasts.

Keep up to date with the Maintainable Podcast by joining the newsletter.

Robby has a chat with Arpit Mohan, the Co-Founder and CTO of Appsmith, an open-source low-code tool that helps developers build dashboards and admin panels very quickly. Appsmith helps businesses build any custom internal application within hours. In regard to well-maintained software, Arpit points to the importance of engineers writing code for humans and not machines while also focusing a lot on readability. He believes useful code comments are also very crucial in facilitating well-maintained software.

Arpit will share his wisdom on the importance of conveying the why over the how behind any code being developed, how open source and closed source projects have different code commenting/documentation needs, why engineers should always keep an eye out for code smells and friction in their ability to deliver software functionality, the problems that AppSmit helps organizations solve, the differences between B2C vs B2B when it comes to the benefits of automated testing, performance concerns, etc, and much much more. Stay tuned, enjoy, and if you like the episode, don’t forget to share.

• The Score Takes Care of Itself: My Philosophy of Leadership by Bill Walsh - https://www.amazon.com/Score-Takes-Care-Itself-Philosophy/dp/1591843472

• https://twitter.com/mohanarpit
• https://twitter.com/theappsmith
• https://www.appsmith.com/

Subscribe to Maintainable on:

• Apple Podcasts
• Overcast
• Spotify

Or search "Maintainable" wherever you stream your podcasts.

Join the discussion in the Maintainable Discord Community

Subscribe to Maintainable on:

• Apple Podcasts
• Spotify

Or search "Maintainable" wherever you stream your podcasts.

Keep up to date with the Maintainable Podcast by joining the newsletter.

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 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!

• The 5 Love Languages by Gary Chapman - https://5lovelanguages.com/
• I Will Teach You to Be Rich by Ramit Sethi -  https://www.iwillteachyoutoberich.com/

• https://www.linkedin.com/in/noahmclark/
• https://twitter.com/nolarknoah

Subscribe to Maintainable on:

• Apple Podcasts
• Overcast
• Spotify

Or search "Maintainable" wherever you stream your podcasts.

Join the discussion in the Maintainable Discord Community

Subscribe to Maintainable on:

• Apple Podcasts
• Spotify

Or search "Maintainable" wherever you stream your podcasts.

Keep up to date with the Maintainable Podcast by joining the newsletter.

Robby has a chat with the Engineering Manager at Planet Argon, Ben Parisot. Ben has worked in the tech industry since 2010 and has worn many, many hats: blogger, web designer, web developer, technical producer, scrum master, technical project manager, copywriter, and more. He loves all parts of the software development lifecycle and always has a creative personal web or mobile app humming along outside of work. The first thing Ben says he looks for that represents well-maintained software is thorough and up-to-date documentation. 

He feels that every developer or project manager must ensure that they leave a good paper trail of the work they do. He encourages engineering teams to do regular documentation audits of internal and external documentation they use in order to find outdated and obsolete documentation. Drawing from his experience working on multiple client projects, his advice is to build processes around auditing and improving documentation to make sure it's effective. This convo will prove incredibly valuable as he shares some tips on how engineering teams can go about that based on the projects they work on and so much more. Don’t miss out!

• Sapiens: A Brief History of Humankind by Yuval Noah Harari

• https://www.linkedin.com/in/benparisot/
• https://www.planetargon.com/about/ben-parisot

Subscribe to Maintainable on:

• Apple Podcasts
• Overcast
• Spotify

Or search "Maintainable" wherever you stream your podcasts.

Join the discussion in the Maintainable Discord Community

Subscribe to Maintainable on:

• Apple Podcasts
• Spotify

Or search "Maintainable" wherever you stream your podcasts.

Keep up to date with the Maintainable Podcast by joining the newsletter.

Robby has a chat with Stefanni Brasil, the Co-founder and Educator at hexdevs, Co-creator of the Get to Senior online course and community, and most recently joined thoughtbot as a developer. Reflecting on her experience in the industry, Stefanni says that well-maintained software can only be a result of teams agreeing on conventions before coding starts. 

She feels that the term technical debt facilitates better communication and her perspective around it has shifted over time due to the fact that most projects that have employed it are the ones that have been generating revenue. Stefanni notes that software engineering teams can work seamlessly when they document their decisions (on Trello, Google Docs, etc) for future reference. Creating an environment where every team member feels safe and comfortable to speak up about any issues also contributes to project success. 

Steffani will also share her knowledgeable insights on how to be a good guest in another team's codebase as a consultant and the steps to take when onboarding with a new client project. She will dive into her Get to Senior course and highlight all the value that it offers. Tune in for more of her software engineering wisdom.

• The Assertiveness Workbook: How to Express Your Ideas and Stand Up for Yourself at Work and in Relationships by Randy J. Paterson

• Fearless Change: Patterns for Introducing New Ideas
• https://twitter.com/stefannibrasil
• https://www.stefannibrasil.me/
• https://academy.hexdevs.com/

Subscribe to Maintainable on:

• Apple Podcasts
• Overcast
• Spotify

Or search "Maintainable" wherever you stream your podcasts.

Join the discussion in the Maintainable Discord Community

Subscribe to Maintainable on:

• Apple Podcasts
• Spotify

Or search "Maintainable" wherever you stream your podcasts.

Keep up to date with the Maintainable Podcast by joining the newsletter.

Robby has a chat with Andrea Goulet, the CEO of Corgibytes, a software development shop dedicated to maintaining and modernizing software applications. Named by LinkedIn as one of the top ten professionals in software under 35, Andrea is the host of the podcast Legacy Code Rocks, is the author of the forthcoming book, “Empathy-Driven Software Development”, has co-founded several successful technology companies, and has taught over 50,000 students how to turn soft skills like empathy and communication into software skills.

Through her newest venture, Heartware.dev, she is on a mission to operationalize empathy for tech teams and keynotes frequently about building a business based on balance, empathy, and trust; the perils of the technical/non-technical divide; and the technical philosophies around working with legacy code. Andrea says that the maintainability of software comes down to trust and while she doesn't find the term technical debt useful, she uses it in instances where it’s being widely used especially in software remodeling projects. From her experience, the term is not useful at all when dealing with business-minded people who view debt differently.

She points out that the success of a project is always highly dependent on the project owner and the team working on their project having shared goals as they approach the writing of software. Robby and Andrea will also dive into why we should avoid deferring to other people and defaulting to being ticket takers, how empathy has different definitions, avoiding us vs them thinking, and so much more. Stay tuned and enjoy!

• Set Boundaries, Find Peace: A Guide to Reclaiming Yourself by Nedra Glover Tawwab

• https://twitter.com/andreagoulet
• https://heartware.dev
• https://corgibytes.com
• Coming in 2023! Empathy-Driven Software Development by Andrea Goulet

Subscribe to Maintainable on:

• Apple Podcasts
• Overcast
• Spotify

Or search "Maintainable" wherever you stream your podcasts.

Join the discussion in the Maintainable Discord Community

Subscribe to Maintainable on:

• Apple Podcasts
• Spotify

Or search "Maintainable" wherever you stream your podcasts.

Keep up to date with the Maintainable Podcast by joining the newsletter.

Robby has a chat with Professor of Computer Science at Stanford University, John Ousterhout. John founded Electric Cloud with John Graham-Cumming. Ousterhout was a professor of computer science at the University of California, Berkeley where he created the Tcl scripting language and the Tk platform-independent widget toolkit and proposed the idea of co-scheduling. Ousterhout led the research group that designed the experimental Sprite operating system and the first log-structured file system. Ousterhout also led the team that developed the Magic VLSI computer-aided design (CAD) program.

When it comes to the maintainability of software, John is more interested in the design aspects of software and feels that indeed the core goal of good software design is to make it easier to maintain software and continually improve it. He explains what problem decomposition is all about and why his course on the art of software design is probably the only one of its kind in the world. 

Join the convo as he also talks about how to write good code comments and why they are so important, the main differences between tactical and strategic programming, how engineers can discuss long-term improvements with their boss, how his curriculum has students approach a project with two different designs before deciding which to proceed with, and so much more. Enjoy!

• Talent is Overrated By Geoff Colvin 

• A Philosophy of Software Design By Professor John Ousterhout
• Tcl/Tk
• John on Twitter
• John’s Webpage

Subscribe to Maintainable on:

• Apple Podcasts
• Overcast
• Spotify

Or search "Maintainable" wherever you stream your podcasts.

Join the discussion in the Maintainable Discord Community

Subscribe to Maintainable on:

• Apple Podcasts
• Spotify

Or search "Maintainable" wherever you stream your podcasts.

Keep up to date with the Maintainable Podcast by joining the newsletter.