The Case For Burning Down Your Application and Starting Over
Wednesday, January 31, 2024 - 4:30 PM UTC, for 1 hour.
Regular, 60 minute presentation
Room: Campsite 6
Nothing built can last forever, as one of the most popular video games in history tells us. And while this quote, usually applies to tangible structures, it also applies to software. But what happens when "forever" is a lot shorter than anyone expected? We try to build software that is flexible, extendable, and adaptable. But, sometimes the technology we chose didn't have the lifespan we expected. Maybe we made some decisions that didn't pan out. Perhaps we had developers who were more interested in getting the job done quickly than properly. Maybe the application was a prototype and never meant for production. At some point, most applications reach their end of life, and no amount of patching or framework upgrades are going to save it. I've had to have the "hard discussion" with clients many times, and I've learned how to deliver this message. We'll see how to measure the cost of ownership of a dying application against the investment of building a new application from scratch.
Prerequisites
Anyone from Architects to End Users who have ever worked with an application that was horribly outdated, poorly designed, and/or in any way not fit for purpose.
Take Aways
- Learn the signs of a failing application (they aren't always technical...)
- How to have this discussion with management aka, the people who control the budget that you're asking for a big chunk of.
- Some strategies that can make the whole "re-platforming" effort go down easier (and maybe less expensive) for everyone.
