I don't have a problem with do-it-all development positions. I'm an advocate of having flexible teams that have access to the entire product. It's usually companies that have walls between teams that are the problem.
This is especially true in the context of smaller companies. Until a place has a decent sized work-force (maybe 50+), you'd expect a lot of full stack type responsibility.
It's also true of places adopting micro-service or modular style architectures.
Other than the "Ninja" in the title I don't see any issue with such a position.
I guess it comes down to "person who can work the whole stack" vs. "single person that will work the whole stack"...better get a therapist before going into the latter 😅
I don't have a problem with do-it-all development positions. I'm an advocate of having flexible teams that have access to the entire product. It's usually companies that have walls between teams that are the problem.
This is especially true in the context of smaller companies. Until a place has a decent sized work-force (maybe 50+), you'd expect a lot of full stack type responsibility.
It's also true of places adopting micro-service or modular style architectures.
Other than the "Ninja" in the title I don't see any issue with such a position.
I guess it comes down to "person who can work the whole stack" vs. "single person that will work the whole stack"...better get a therapist before going into the latter 😅
I don't have any problem with Full Stack positions too, as long as I'm not the only developer.
I've been into IT since 1999.
Started off with HTML, CSS and MS notepad.
I've been doing Ops since 10 years. I work with Unix, Linux, Web Server, Databases, Docker, Kubernetes. You name it.
I transitioned to Web Development and I'm into Node, React and Javascript. I like Rails and I've been building with Django and Flask.
Doing Full Stack in a 50+ team, well, that's another story. I'll take that.
Yet, I won't take a job where I'm supposed to do all of those, alone.