I've been doing some front end to back end integration for my friend's side project. I noticed that when you account for me doing the backend stuff (identity, databasing, modelling, etc) and then when you factor in that I'm the only one who can integrate the data services to the frontend, and you further account having to do validation and round trip debugging, Im pretty much doing all the work. So I decided to get down and dirty with the front end, as he had suggested NextJS. I just have no words sometimes for the cryptic bullshit i have to witness, hidden conventions, file loaders for everything, what the fuck is the difference between babel and gulp. Im trying to link data not gulp dowm some sprite niggas.
And as sad as it is, i can fully see why front end devs make less money: when you take away their fancy front end toys, they cant really do much else. Full stack was just a jewish way of shoving two jobs into the price of one. But then you see idiotic crap like the NextJS convention bragging about inline SQL ... as if backend systems never warned about non sanitized data. It's like Full Stack being made by front end devs ends in a complete disaster. A good example, one of the requirements for the project was a multi tenant environment that could simulate virtualized tenants/organizations within the app. Good luck coding that shit in the front end with your shitty NodeJS system
And that's how you know it for what it is. When it becomes part of the FotD bullshit spouted by know-nothing MBAs. Or, you know, idiot diversity hires.
PotatoWhisperer2 0 points 1.5 years ago
And that's how you know it for what it is. When it becomes part of the FotD bullshit spouted by know-nothing MBAs. Or, you know, idiot diversity hires.