Remove any passion from the discussions and at the end focus on reducing costs, you'll get your migration. It's a long process but if you take time to discuss. I produced swot analysis, risk analysis, benchmarks on component libraries (we went with zendesk garden), cost of development per feature. I then had to do different presentations and discussions about architecture and costs. I also showed that the standard stack with nextjs and react was to use in place of ember data: redux toolkit (you could choose react-query depending on your needs)Īt the end of this meeting, people were excited but still had questions. Then I pitched that Ember Data along with nextjs and react was a viable solution. I pointed out that I had experience with react and nextjs but not with embroider. I explained what was embroider and how it compared with nextjs. Track how you spent your time on a computer. This is enough to determine when and how much you did something. You can get information on what apps were used - exactly at what time - and what title the application had at that moment. Then I showed why ember cli was old and there was this new cool kid embroider that we will need to migrate in the future. With Tockler you can go back in time and see what you were working on. This is the fastest route from Lewistown, MT to Butte, MT. Lewistown and Butte are 4 hours 21 mins far apart, if you drive non-stop. ![]() I then explained that we could just live with ember data, ember cli and react. There are 164.79 miles from Lewistown to Butte in southwest direction and 247 miles (397.51 kilometers) by car, following the I-90 W and US-191 S route. I then explained that most of our components were ember components wich are deprecated and need to be migrated anyway ![]() I compared it to glimmer components and ember components. The way I started my introduction is by explaining what is react. I was in the same situation and managed to migrate to react+redux toolkit+nextjs.
0 Comments
Leave a Reply. |