Yes, a front end dev needs to focus much more on structuring the event-driven data or "real-time recording". The backend dev will take that JSON and build SQL queries or feed it into memory, which they can take their time for the most part, unless it is an API or something. Building data relationships within a browser is super tricky and deals a lot with immutability and templating view plus middleware type development.
A front end dev needs to know design patterns and follow them to a tee or their project could go up in smokes. React itself has Shards, PureComponents, HOC's, or building a ComponentFactory. I mean you can say that backend could be harder but after wrestling with React and libraries like Redux, I quickly realized that Front end devs are not just playing around with for loops to make scrolling menus. Front end devs are the new Mad Scientists.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Yes, a front end dev needs to focus much more on structuring the event-driven data or "real-time recording". The backend dev will take that JSON and build SQL queries or feed it into memory, which they can take their time for the most part, unless it is an API or something. Building data relationships within a browser is super tricky and deals a lot with immutability and templating view plus middleware type development.
A front end dev needs to know design patterns and follow them to a tee or their project could go up in smokes. React itself has Shards, PureComponents, HOC's, or building a ComponentFactory. I mean you can say that backend could be harder but after wrestling with React and libraries like Redux, I quickly realized that Front end devs are not just playing around with for loops to make scrolling menus. Front end devs are the new Mad Scientists.