Technical Debt isn't Free

While many computing systems mirror systems in nature, one aspect that doesn’t is technical debt. The majority of spending is maintaining the existing systems, and yet very little attention is paid to how to reduce the on-going costs. SHOW: 558 CLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotw CHECK OUT OUR NEW PODCAST - "CLOUDCAST BASICS" SHOW SPONSORS: phoenixNAP website phoenixNAP Bare Metal Cloud Platform CBT Nuggets: Expert IT Training for individuals and teams Sign up for a CBT Nuggets Free Learner account SHOW NOTES: Fall Colors in NC Mountains Succession Session 3 (HBO) GitLab goes IPO IN NATURE, THE FALL BEGINS THE PROCESS OF RESETTING In many parts of the world, Fall (or Autumn) gives us a last glimpse of the beauty of nature, but then it resets for another cycle of recuperation and regeneration. This is one of the aspects of nature that the tech industry doesn’t seem to emulate in their systems. WE ACCEPT RESETS AND CHANGES ALL AROUND US, EXCEPT IN IT Why don’t we create “life cycles” on commonly deployed systems? Why don’t we prepare people for resets and “leap forwards” better? Why isn’t there a part of our industry that attempts to innovate in this space, rather than just shift it to another party as “someone else’s problem”? Why do we assume the same needs (support, uptime, etc.) of the technical debt as we do the new things we build to replace it? FEEDBACK? Email: show at the cloudcast dot net Twitter: @thecloudcastnet FEEDBACK? Email: show @ the enterprise ai show dot com Bluesky: @TheEntAIShow.bsky.social Twitter/X: @TheEntAIShow Instagram: @TheEntAIShow