This is maybe getting offtopic but I still have no idea why the term "full stack developer" exists or why it's so widespread. Sure, if you specialize in JavaScript and you mainly work writing web UI libraries, you might mainly consider yourself a "frontend developer." Same thing for working on server frameworks that would, I guess, make you a "backend developer"? (I'd think in that case you'd probably just be into general programming, and not call yourself that)
Does a person that wires up a backend to do some business logic, hit some APIs, etc. and then send it to a frontend to be displayed really need a name like "full stack"? It almost implies your doing both of the jobs of a frontend and backend developer, but if you go by the example work I mentioned previously, you're not doing that. That's what I do for my job and it feels like I'm doing the Sesame Street of programming jobs compared to other areas of the industry.
I don't like how the term "software engineer" is overused either. Maybe just cause most of what comes out of the software industry really shouldn't be compared to what comes out of industries that build bridges and large machinery. I don't feel like people who regularly joke about copy-pasting code snippets from Stack Overflow are really implementing proper engineering practices.
> I don't feel like people who regularly joke about copy-pasting code snippets from Stack Overflow are really implementing proper engineering practices.
I think most people say this in jest; regardless, writing low-effort code that would be "helped" by this practice is just a small part of the job anyways.
As a backend dev, I probably know which teams are calling me but not necessarily why, and I rarely have occasion to try to read their code. I can’t call myself full stack because I haven’t seriously touched frontend for a while and it changes rapidly.
Does a person that wires up a backend to do some business logic, hit some APIs, etc. and then send it to a frontend to be displayed really need a name like "full stack"? It almost implies your doing both of the jobs of a frontend and backend developer, but if you go by the example work I mentioned previously, you're not doing that. That's what I do for my job and it feels like I'm doing the Sesame Street of programming jobs compared to other areas of the industry.
I don't like how the term "software engineer" is overused either. Maybe just cause most of what comes out of the software industry really shouldn't be compared to what comes out of industries that build bridges and large machinery. I don't feel like people who regularly joke about copy-pasting code snippets from Stack Overflow are really implementing proper engineering practices.