this post was submitted on 23 May 2025
461 points (98.3% liked)

Programmer Humor

23417 readers
1776 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

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 79 points 21 hours ago (4 children)

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

[–] skisnow 1 points 43 minutes ago

A significant percentage of developers regard frontend dev as a branch of the Arts, and therefore not "proper" software engineering.

I once had a fresh grad Junior complain to me about being given a frontend ticket, because they wanted to be writing Real Code and apparently thought they were too good to learn how to change the margin on a div.

[–] [email protected] 22 points 17 hours ago* (last edited 16 hours ago) (3 children)

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.

[–] [email protected] 4 points 10 hours ago (1 children)

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.

[–] [email protected] 2 points 1 hour ago

All the node.js backends reading this rn

[–] [email protected] 9 points 14 hours ago (1 children)

In particular, frontend has to interact with humans, which is one hell of a messy API.

[–] [email protected] 2 points 1 hour ago

Can confirm. I’m a full time frontend developer and humans don’t have very well defined APIs

[–] [email protected] 3 points 16 hours ago

And, while tested to extreme limits, somehow the end user still finds ways to break it, creating more things haphazardly stuffed in

[–] [email protected] 35 points 21 hours ago

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.

[–] [email protected] 17 points 21 hours ago (3 children)

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

[–] [email protected] 12 points 17 hours ago (1 children)

Management: "We're only going to hire 'full stack' devs from now on."

Also Management: "Why is this page taking 37 seconds to load?"

[–] [email protected] 4 points 16 hours ago

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.

[–] [email protected] 8 points 16 hours ago

The security and permission layers for the API:

[–] [email protected] 4 points 18 hours ago

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.