3 ms·

>If you’re unlucky, you might read this and think, “holy shit, no wonder I’m burned out”. This is why full stack jobs are terribly compensated for workers. Eve

>If you’re unlucky, you might read this and think, “holy shit, no wonder I’m burned out”. This is why full stack jobs are terribly compensated for workers. Even worse if you are doing infrastructure. Companies are not paying a premium for the flexibility and likely burning you out at the same time.

irrational 3y ago
My previous job was a full stack developer, but I had built the entire product from front to back on my own and knew how it all worked. I found it quite easy and even enjoyable. Now I'm working a job that is not full stack and I'm finding it extremely stressful because I didn't build the thing and still haven't figured out how the different parts work, much less work together.
- karmakurtisaani 3y ago
  If it makes you feel any better, there's now a person in your old job being stressed the same way!
Terr_ 3y ago
My own litmus-test for "full stack" (which may be a lower bar than for some others) isn't that the person can whip up a full stack of anything anywhere, but that they know enough to trace problems up and down through the stack. Ex: The visual bug caused by the CSS style applied by the JS code that operated off the data from the server from this call which came from that database query which was bad data because of that process which was triggered by this call that comes from that UI button, etc.
- diarrhea 3y ago
  Interesting. By that definition I’m full stack, despite never having written TypeScript from scratch (just some htmx stuff). But that’s only fair, seeing how there’s plenty people calling themselves full stack without ever having written a single Dockerfile line. They couldn’t deploy themselves out of a wet paper bag. Maybe I shouldn’t what other people call themselves get to me so deeply, huh.

3 ms·

>If you’re unlucky, you might read this and think, “holy shit, no wonder I’m burned out”. This is why full stack jobs are terribly compensated for workers. Eve

by vsareto 3y ago

irrational 3y ago
My previous job was a full stack developer, but I had built the entire product from front to back on my own and knew how it all worked. I found it quite easy and even enjoyable. Now I'm working a job that is not full stack and I'm finding it extremely stressful because I didn't build the thing and still haven't figured out how the different parts work, much less work together.
- karmakurtisaani 3y ago
  If it makes you feel any better, there's now a person in your old job being stressed the same way!
Terr_ 3y ago
My own litmus-test for "full stack" (which may be a lower bar than for some others) isn't that the person can whip up a full stack of anything anywhere, but that they know enough to trace problems up and down through the stack. Ex: The visual bug caused by the CSS style applied by the JS code that operated off the data from the server from this call which came from that database query which was bad data because of that process which was triggered by this call that comes from that UI button, etc.
- diarrhea 3y ago
  Interesting. By that definition I’m full stack, despite never having written TypeScript from scratch (just some htmx stuff). But that’s only fair, seeing how there’s plenty people calling themselves full stack without ever having written a single Dockerfile line. They couldn’t deploy themselves out of a wet paper bag. Maybe I shouldn’t what other people call themselves get to me so deeply, huh.