Don't Rip and Replace: how to avoid the shiny upgrade pitfall in long-term systems

"But when we move off CodeIgniter and onto Laravel, that'll fix all the little bugs"

"Check out this new JS Framework; it'll improve our dev productivity"

"The vendor assures me the migration to this new ERP will be painless, and the ROI will pay off in 3 years"

For long-running systems, upgrades are often more painful than they're worth.

But what's the alternative? Sticking with old, crusty code from yore?

We'll discuss why upgrading is painful, different options for upgrading, and finally, ways we've found to not upgrade.

Come and share your upgrade experiences. Come and learn why we're still running a project on 2010's latest technologies - Grunt and Bower - and why we have forced ourselves to not upgrade.

• Intermediate
• Development
• Product
• Other