This is a very good example. Yes you can re-write it, and assuming you succeed, you may not know the future direction and by making assumptions to make things e

This is a very good example. Yes you can re-write it, and assuming you succeed, you may not know the future direction and by making assumptions to make things easier very much lock yourself out of those options. Also, its possible you pick a stack that causes all kinds of re-training, contracts to die, systems to redo, that doesn't scale to the number of production users, has other unexpected costs, etc. maybe the code is written fast but is hard to maintain. Maybe you have vendor agreement. maybe you have client agreements about where the database can be located. Who knows. Lots of variables. And you can't see this beforehand. Never ever do this without at least some management buy-in. Someone who is on board with you and can help better define the requirements and explain why things are done this way