this post was submitted on 14 Dec 2024
-26 points (40.2% liked)
Programmer Humor
19804 readers
59 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
As a backend engineer who has experience with frontend I've learned it's two things
From an engineer's point of view, if they call themselves a full stack engineer they're usually a front end dev who have written a few apis in the past. No shame, but I've seen way too many people say they're backend without fully understanding what being a backend engineer really is in terms of scale, speed, and flexibility.
From q businesses point a view, a full stack engineer is a role they made up that means "we expect an expert in all areas but want to pay a lower rate".
Both areas need experts. I'd say I'm an expert in backend. I think it's impossible to be an expert in everything, and companies who want "full stacks" should expect jack of all trades master of none, and will attract literally any engineer, because what the hell is full stack.
I've probably pissed off a lot of fellow engineers, but I guess what I'm trying to say is be a master of your domain. Learn how frontend and backend work, but don't try to be an expert in everything. It's good to specialize. When you're asked if you are a full stack engineer it's perfectly fine to say "I have experience in the full stack, my expertise is on the backend, but I can do react when needed"
There are both kinds of full stack developers: the frontend dev that doesn't understand the backend enough to know they suck at it, and the backend dev that doesn't understand the frontend enough to know they suck at it.
I couldn't agree more with the latter part, I know a lot of backend engineers who consider frontend simple without ever trying what it really takes. This is not a healthy way to view someone else's work, and it usually produces friction between back and front end teams
You can always spot them when they have to ask about state.
I always asked about state.
Backend engineer here who got gud at frontend because of mobile, but recognize others are way better than me at it.