DEV Community

loading...
Cover image for Some-Stack Engineer

Some-Stack Engineer

nickytonline profile image Nick Taylor (he/him) Originally published at iamdeveloper.com Updated on ・1 min read

Photo by Bill Oxford on Unsplash

Anybody down for starting the some-stack engineer movement?

In all seriousness, no one can really be full-stack these days.

Captain America saying he can do this all day

There are too many moving parts. Frontend, design, backend, database, deployments, automation etc. I think it comes down to you are good at some of the stack.

Thoughts?

Discussion (10)

pic
Editor guide
Collapse
steveblue profile image
Steve Belovarich

Full-stack was in for awhile but it seems companies have been veering back toward specialization (with the exception of small startups).

I believe it is a good thing to collect some experience in all the things, but always have some area you excel at. Master some skill and find a team that needs that thing you do and appreciates you for who you are.

Collapse
nickytonline profile image
Nick Taylor (he/him) Author

Yeah, I hear ya. I've worked at small startups and you wear many hats because you're helping out. Last place I was at, I was hired as a frontend dev, but doing frontend/some backend, but at the same time helping with Kubernetes updates and deployments.

Now at a bigger company, it's pretty much just frontend I'm doing. Sometimes I touch the backend if it's related to a ticket I'm working on.

Collapse
samosborn profile image
Sam Osborn

I work for a small education non-profit with a two person software team. We are both full stack, and it's wonderful. The only black boxes that exist are the only ones we make for each other. It keeps us honest and humble. From both a design and tech support perspective, work is efficient, clear, and self-managing.

I expect, in addition to start-ups, a lot of in-house IT professionals that work outside of the software contracting sector have a similar experience.

I think of it less as full-stack and more as village-style, or anarchic. Hierarchy and specialization exchanged for consensus and understanding.

Collapse
richardj profile image
R☭

If the company is very small (or a personal project) you can do the full-stack, but doing that in a scaling company (in whatever way) it is just not really possible. Jack of all trades, master of none.

We also do not see any 'full-stack' anything in other careers.

Collapse
ajonp profile image
Alex Patterson

Just be a broken comb 😁

Collapse
alexparra profile image
Alex Parra

I call it broad-stack.

Collapse
clavinjune profile image
Clavin June

I am now titled as "software engineer" in my workplace which means "full-stack". But i never handle devops ticket or anything, maybe the term of fullstack is different at different places, wdy think?

Collapse
gklijs profile image
Gerard Klijs

Not sure different places. Both sometimes it's just frontend and backend development what they mean. And sometimes it's just backend and ops. So I rather say 'I have done mainly backend, but also some frontend, ops and testing. Then saying I'm full stack.

Collapse
khalalw profile image
khalalw

I agree... obviously lol.

Collapse
prasannamesta profile image
Prasanna Mestha

lmao. It's funny but It definitely makes sense