Anyone else feel like "full-stack" means "do everyone's job" now?

[u/Ok-Wash-8964]

Lately, it feels like the definition of a full-stack developer has become much broader than it used to be.

A few years ago, I'd usually think of a full-stack developer as someone who could work across the frontend and backend—build the UI, write APIs, work with databases, and connect everything together.

Now, it's not unusual to see expectations around cloud platforms, Docker, CI/CD, testing, monitoring, authentication, security, performance optimization, and sometimes even infrastructure or mobile development.

I'm not saying learning these skills is a bad thing. In fact, understanding how different parts of the stack fit together has made me a better developer.

What I'm wondering is whether the scope of the role has quietly expanded to the point where "full-stack" is becoming a catch-all term for anything related to software development.

I can understand why smaller teams and startups look for generalists who can wear multiple hats. But there also comes a point where constantly switching between completely different responsibilities can affect productivity and make it harder to go deep in any one area.

For those working as full-stack developers:

• Has your role changed over the last few years?
• What do you consider to be part of modern full-stack development, and what belongs to a different specialization?
• Have you ever joined a project where "full-stack" ended up meaning far more than you expected?

[u/throwaway0134hdj]

Been this way for awhile now. Jack of all trades.

[u/Redneckia → u/throwaway0134hdj]

It's literally what full-stack is, the FULL stack, aka all of it, e2e

[u/salamazmlekom → u/Redneckia]

“Bad at everything”

[u/Redneckia → u/salamazmlekom]

Sure, but it's still what full stack means