I Almost Got Fired for Choosing React in Our Enterprise AppReact was supposed to ease our development. Instead, it created roadblocks
I Almost Got Fired for Choosing React in Our Enterprise App React was supposed to ease our development. Instead, it created roadblocks Razvan Dragomir Photo by Samuel Bourke on Unsplash It’s summer 2018. My boss, Adrian, asks me to join him in a Skype call with James, the CTO of a big Canadian company. While getting to know each other, I find out that James is a smart guy with big ambition. His vision is to migrate a massive desktop WPF application to the web in the cloud. I like his friendly attitude and I can tell that he is eager to collaborate with us. He already has a development partner in India, but they lack experience in building web applications. Adrian and I follow the standard approach for this situation. We have a few more calls and then we start the discovery phase in which we try to grasp the big picture and find the non-functional requirements. These are the main points we should focus on: A big application — more than 220 pages, most of which are maintenanc
