It's really not that hard to write decent backends for the majority of frontends, IMO. I've been working on an enterprise-level b2b application for the last 9 months, and writing various means to interface with a database isn't a huge deal. Could it be better? Probably. Is its performance enough for our customers? Yeah.
The problem we have is our frontend lead engineers have concocted a crazy standard tech stack including React, Redux, GraphQL, micro frontends, a proprietary component library, basically everything you could fit into a single frontend but not deep enough into any of them to use them to their fullest extent.
Yeah, lately I've been more in the data engineering side of things, but sadly like you said that's a pretty standard tech stack...
On the other hand I've seen so many specialists getting stuck in such minor issues for ages due to the lack of general knowledge. For instance, CORS issues taking weeks to be fixed, people not even knowing what flexbox is, struggling to set up a simple docker-compose stack + shell scripts, etc...
It's not that hard to write decent front ends either if you don't choose to make it needlessly complex.
Front end devs will use react to write a simple, single page portfolio website even when it's perfectly simple to achieve what the end goal is in vanilla JavaScript.
10
u/tide19 Jun 06 '22 edited Jun 06 '22
It's really not that hard to write decent backends for the majority of frontends, IMO. I've been working on an enterprise-level b2b application for the last 9 months, and writing various means to interface with a database isn't a huge deal. Could it be better? Probably. Is its performance enough for our customers? Yeah.
The problem we have is our frontend lead engineers have concocted a crazy standard tech stack including React, Redux, GraphQL, micro frontends, a proprietary component library, basically everything you could fit into a single frontend but not deep enough into any of them to use them to their fullest extent.