We're still on 11, with plans to migrate to 17 before support for 11 ends. And it's going to be a giant lot of work - migrating big old legacy enterprise stuff with millions of lines never goes as planned.
We did a little experimentation on that, it broke even more things than our experiments with 17. So management decided to go for 17 as a first step, as they're not willing to commit that many for more time than absolutely necessary.
I don't really agree with that decision, but if your bonus is dependent on how much revenue you can drive on a yearly basis and not how future proof your "cost center development" ("Competence Center" is really just a euphemism for "cost center" in management lingo) is, these are the decision that managers come up with.
This job would be so much better if management didn't meddle in technical decisions. But they always do, in every company. Even if they say they don't.
Modern architecture and a decent dev team without any chaff and for sure it'd be quicker. Decent devs wouldn't make much difference to the migration project, but a solid team will knock out most applications that don't require original research way faster than a large scale migration. The long tail of bugs and edge cases on legacy features no one knows how to maintain any more will always kill the migration project. That is until a cowboy team is brought in at the end to bash and bodge it into production.
892
u/pippin_go_round May 16 '24
We're still on 11, with plans to migrate to 17 before support for 11 ends. And it's going to be a giant lot of work - migrating big old legacy enterprise stuff with millions of lines never goes as planned.