this post was submitted on 07 Mar 2024
647 points (95.4% liked)

Programmer Humor

19488 readers
237 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 1 year ago
MODERATORS
Feyter@programming.dev
anzo@programming.dev
BurningTurtle@programming.dev
pylapp@programming.dev
647
Full Stack Programmer Doing Frontend (programming.dev)
submitted 8 months ago by LinearArray@programming.dev to c/programmer_humor@programming.dev
96 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[โ€“] RiikkaTheIcePrincess@pawb.social 9 points 8 months ago (1 children)

Came here to ask if I'm the only one grossed out by the term "full stack" and its exploitative implications. Thanks for explaining why :3

Hey, maybe they make up the difference in "exposure" or something! That's a well-loved way to ask for free/underpaid work!

[โ€“] azertyfun@sh.itjust.works 3 points 8 months ago

I love shitting on Fullstack devs as much as the next guy. However, sometimes it really just does make sense for an (often internal) product maintained by a one-person team, and it doesn't have to mean that the organization doesn't value them. I've seen it happen.

However I would not recommend it as a career path because it's essentially impossible to tell what you're getting into when you get hired. Could be what I just described, could be that you inherit the full responsibility for a 20 year-old perl+php5+xhtml+angularJS mess.
I think it can only truly make sense if you work independently and get to build projects to your own quality standards, assuming you manage to find a "scope is small enough that specialization doesn't make sense" niche. This is very hard which is why in practice "full stack" tends to mean "master of none but good enough to get a product out the door cheaply".