3 ms·
No advice per se, but questions you'll want to consider as you read others posts: 1. why do you believe you can build it better? (even with the most amazing te
by alberth 2y ago
No advice per se, but questions you'll want to consider as you read others posts:
1. why do you believe you can build it better? (even with the most amazing team)
2a. its easy to over-estimate the gains of a rewrite, and dramatically under-estimate the negatives. how bad could things get, for the business, if you migrated to a worse solution? (lost revenue, lost customers, etc)
2b. after you answer #2a, do the gains (of a rewrite) now really seem so big?
3. if you outsource this rewrite to a 3rd party (freelance, contractor, etc) - how is that any different than today? you're already "outsourcing" this to an existing vendor. How would you maintain code from non-employees?
4. can the business even support the cost (and it's a positive cost/benefit analysis) on hiring full-time employees to rewrite and maintain this code base - forever.
5a. what do your competitors do? (buy the same vendor software or they built their own)
5b. if they use the same 3rd party vendor, is the market big enough for you to turn this into a new revenue generating business (sell this in-house app you'd build)?