This is an interesting breakdown of technical debt as you'd actually see it in a real, production site. Crufty systems to rip out and replace with frameworks, databases which were being shared across applications, data migration (I feel your pain), etc.
On the plus side, after you get good at using a framework, you tend to accumulate a lot less debt. The downside is that your first project with a framework probably incurs more debt than you would otherwise, although if "otherwise" is a using a home-brewed flat-file DB you might come out net positive anyhow. ;)
I've ripped out almost 70% of the code that was in the first commit for the Rails version of the Bingo Card Creator over the years. (I did not know you could serialize an array in the database, so instead, I wrote it to a ... home-brewed flat-file DB...)
On the plus side, after you get good at using a framework, you tend to accumulate a lot less debt. The downside is that your first project with a framework probably incurs more debt than you would otherwise, although if "otherwise" is a using a home-brewed flat-file DB you might come out net positive anyhow. ;)
I've ripped out almost 70% of the code that was in the first commit for the Rails version of the Bingo Card Creator over the years. (I did not know you could serialize an array in the database, so instead, I wrote it to a ... home-brewed flat-file DB...)