Building Code More Responsibly: A Mental Model Shift

May 8, 2022
A philosophical conversation around building code more responsibly and how ethics and accountability is to be integrated into the DevOps industry.

This week on Adventures in DevOps, we had a bit of a philosophical conversation around building code more responsibly and how ethics and accountability is to be integrated into the DevOps industry. Eric Tank joins the show and shares his perspective on how to “develop for deprecation”. Building a code that is documented, tested, monitored, and deployed is important, but can you easily pass it off to someone else, or be able to walk away from the code it entirely? Johnathan joins by saying that “software is never done until it’s deleted.” They finish the discussion referencing apprenticeship models and how accountability in this way could parallel other industries.

Listen now!

Related Content

What's the ideal ratio of devs to QAs?

Of course, as a consultant, I can confidently tell you: It depends!

Short-term alternatives to code freezes

Use a code freeze as a reminder that there are still quirks to be worked out, and make an effort to work them out.

Adventures in DevOps 114: Progressions Through Programming Languages

What are the types of program languages required in DevOps? What are the pros and cons of each?