Abstract
As we move into the era of AI, code that could be called slop or tech debt is increasing faster than ever. This means that managing that tech debt is just as important as ever. However, how do you prioritize which tech debt to work on? How do you convince others that any of it is important? In the world of AI, is it important? Our goal at the end, is not to eliminate tech debt, but to write the best software we can for the situation in which we find ourselves. In some cases this means more tech debt, in others, less. In this talk, I'll discuss how to think about prioritizing tech debt, how to create a business case for your tech debt, and how AI may or may not color any of this.
Speaker
Joy Ebertz
Principal Engineer @Imprint, Blogger, and Speaker, Previously @Harness, @Split, & @Box
Joy is a Principal Software Engineer at Imprint where she is currently trying to detangle their configuration. She is a primarily backend focused developer with extensive experience in configuration, microservices architecture, revamping authorization frameworks, creating REST API standards, audit logging and more. Prior to Imprint, she has worked at Harness, Split, and Box in Staff+ roles. In addition to designing software and writing a lot of code, she also maintains a blog: joy.ebertz.run/blogs.html (with both career and technical topics). In her free time, she does a lot of traveling, reading, and running ridiculously long distances (mostly on trails).
