Full Stack Developer

This is quickly becoming the norm in every industry. Every employer wants fewer employees to do more, without paying them more of course.

It's not just developers. I'm in web marketing and I'm expected to do front end work including creating figmas and writing code. This is along with my regular duties as a marketer.
- What's figma?
- I'm falling into that myself... It seems my boss is trying to prevent me from being Pidgeon-holed into being just a programmer.
  
  Aka, he is diversifying my portfolio to keep me on board as an employee.
  
  Guess it helps some full-stack'ers if they also have experience in graphics design and copywriting.

I work full stack and even do dev operations and my title is not "full stack" and I believe the reason why is so HR can argue to pay me less.

The only way to get what you're worth is to change jobs. Then do it again in a couple more years.
Why would you think full stack developers make more money in general?
- Eh, this is a thing, large companies often have internal rules and maximums about how much they can pay any given job title. For example, on our team, everyone we hire is given the role "senior full stack developer", not because they're particularly senior, in some cases we're literally hiring out of college, but because it allows us to pay them better with internal company politics.
- They do according to can stats
- Because we’re old bastards who remember before React.
- That really depends on the company. At big tech companies, it's common for the levels and salary bands to be the same for both generalists (or full stack or whatever you want to call them) and specialists.
  
  It also changes depending on market conditions. For example, frontend engineers used to be in higher demand than backend and full-stack.
- At the moment it looks like what the market is demanding. A few years ago specialisation was in
What’s it then? 3/4 stack developer?
- Just web, which is bullshit cause i literally work with like 3 OSs and 5 programming languages, ci cd. I just get thrown into a random project and come out with solutions. I told my manager my title should be software dev but he disagreed, shucks I guess.

My situation, give it to the “computer” guy.

I'm not even in tech. I teach maths at night school to support myself while doing my masters. Somehow I've become the 'computer guy' at my job. All the teachers and even office staff ask me to explain software to them that I myself have never even used. I need to learn to say no.

can anyone explain to a hobby programmer?

the term normally refers to a developer that can be productive in every layer required for a typical application to work.

They can do the front end design/styling/implementation and are familiar with front end languages and frameworks

They can do the backend API design and are familiar with the typical backend languages and patterns.

They can do the database table design, write and optimize queries.

They can handle the ci/cd scripting that handles building and deploying the application

They can design and write the automation tests and are familiar with the libraries used for that.

And a bunch of other crap like load testing or familiarity with cloud services.

The latest thing added to the list is AI model creation which is a nightmare.. but, I can't say no 🤷‍♂️
- Also, in practice, they're usually only good at one or two of the things on the list (at best) and hack their way through the rest. As much as people make fun of overspecialization, it happens in every field for a reason.
- Start saying no. If you don't know how, start learning. It's hurting everyone up and down the industry.
  
  I am almost purely focussed on creating DNNs ("deep neural networks" for the unaware) and it's almost always a nightmare work-wise, even without all the rest of the other crap.
- The latest thing added to the list is AI model creation which is a nightmare.. but, I can't say no 🤷‍♂️
  
  That's funny, I'm working with AI models for my thesis. Good to know that professional programmers struggle with it too.
They develop software on Marshall Full-Stack amplifiers, rather than the smaller, less powerful Half-Stacks.

Hope that helps clear things up.

This is why I stopped identifying myself as full-stack and only do front end.

so you put up a front?

As a Jr. Full Stack, I'm in this picture and I don't like it.

I used to work as a full stack developer 😢

I've always been full stack and feel like I'd be bored just focusing on one area. am I deluding myself?

I'm thankful I am full stack and can do my stuff across borders. I hate the interfaces, waiting for stuff, or being hindered by dissatisfactory (to me anyway) stuff from them. So I'm glad when I have control over the entire stack - from talking to the customer to running production.

Anything I don't have control over - most if it doesn't get done, the rest can be okay or bothersome.

I hate that I don't see what the admin set up and does on the infrastructure. It makes it harder to assess issues and potential issues and how they could correlate with infrastructure changes and activities..

For me that's the wrong way around.

I want to be able to fix the issues I see. I hate it when I can't.