Thank you, this was very helpful. "Second, you don't have to tackle everything at once. Don't touch SCSS until you have a good grasp on standard CSS. Don't wor

Thank you, this was very helpful. "Second, you don't have to tackle everything at once. Don't touch SCSS until you have a good grasp on standard CSS. Don't worry about Flow until you have a _really_ good handle on Javascript. Don't try to pick up Redux until you've got a good understanding of React. And, with tools like Create-React-App, you can start up a React project without having to worry about Webpack or Babel until you're ready to look at how they're configured." This is the plan but also the root of the issue. I was trying to learn things as needed but I feel like it was more confusing that way. I decided to get a more solid understanding of each thing but when I start to plan out my time it is way too long. The best case I learn everything around the same amount of time I was planning to finish the POC which also includes the API, DB, and embedded programming. I going to stick with it for now. My main question is does elm have a smaller surface area of things to learn and if so is it a big enough difference to make up for the better react resources?