500% of every “replace the legacy system” project is even discovering what the legacy system does.
There are no specs. Well, they are, but they’re wrong and onsolete, and never encompass use cases that you didn’t even know were going on and only appear when you switch over and people scream that the tools that use an embedded copy of Opera for the Nintendo Wii to access their financial services break.
Yeah, currently going through this with a legacy authentication platform. 100% correct
But, if you are willing to just break everything and fix only the parts that you realize as important afterwards, and not offer any compromises or solutions to legacy shit. You can just replace it quickly. I think that’s what is going to happen here.
If things are actually broken, things get fixed a lot quicker than if you tell people you are going to slowly migrate out.
This is the right way to do any of those migrations. Insisting on absurd legacy capabilities is one of those things people will say it’s important and want to bill for but adds no value. Just load archive data and start fresh with the workflows that are still pertinent.
500% of every “replace the legacy system” project is even discovering what the legacy system does.
There are no specs. Well, they are, but they’re wrong and onsolete, and never encompass use cases that you didn’t even know were going on and only appear when you switch over and people scream that the tools that use an embedded copy of Opera for the Nintendo Wii to access their financial services break.
Yeah, currently going through this with a legacy authentication platform. 100% correct
But, if you are willing to just break everything and fix only the parts that you realize as important afterwards, and not offer any compromises or solutions to legacy shit. You can just replace it quickly. I think that’s what is going to happen here.
If things are actually broken, things get fixed a lot quicker than if you tell people you are going to slowly migrate out.
This is the right way to do any of those migrations. Insisting on absurd legacy capabilities is one of those things people will say it’s important and want to bill for but adds no value. Just load archive data and start fresh with the workflows that are still pertinent.