this post was submitted on 23 May 2025
417 points (98.4% liked)
Programmer Humor
23417 readers
1635 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Funny, most people I've talked to said that the backend code usually is better structured and written, while the frontend (web and games) was a hot mess
Yeah, that’s my experience. The backend is an environment you control completely and has well-defined inputs and outputs specifically designed to be handled by machines. Front end code changes on a whim, runs who the hell knows where, and has to look good doing it.
Plus for the front most people use very unsafe languages and glued together frameworks (JavaScript, typescript, react, Vue etc), whereas on the backend we can use proper type-safe, compiled languages with better abstractions (rust, scala,...) with proper unit and integration tests.
In particular, frontend has to interact with humans, which is one hell of a messy API.
And, while tested to extreme limits, somehow the end user still finds ways to break it, creating more things haphazardly stuffed in
Depends who's coding what. Since fullstack, ick, is the norm, backend coders forced to do frontend is the case that you've described. Frontend coders forced to do backend is the case in the comic.
My experience has often been that Business mostly cares about what they and their users can directly interact with (The FE) and don't really care about spending time and effort on the BE
The security and permission layers for the API:
Management: "We're only going to hire 'full stack' devs from now on."
Also Management: "Why is this page taking 37 seconds to load?"
I'm now a full-stack engineer. Instead of being ok at any layer, I don't know what I'm doing in the UI, the Service, the Backend, the Database, the Cloud Infrastructure, and the CI/CD.
But, if anything breaks, I almost always can figure out where it broke very quickly. A fix is always unpleasant though.
Yes, but that also means backend developers only have to worry about the code. Where I work, they always align on best practices across the company. While frontend is a mess of apps and frankensteined components.