What are your thoughts on this?

I'm just going to leave this here.

https://devrant.com/rants/2483376/...

As with everything, one may only be starting being full stack developer. To me, it's more of desire rather than objective title.

I have to agree if i'm to be honest.

I've met plenty of "full stack" developers who don't understand servers and networking in any way shape or form, many seem to think that the "stack" is just their favourite framework and that's all.

I hired one once (he stated he had all the relevant skill through the interview process) and plopped him in front of a computer and said I'll let him get set up how he likes it (OS and all, though we start everyone on Windows and leave them to change it if they wish) while I went for a meeting.

I came back 2 hours later and he'd done nothing, had no idea how to set up a web server, I asked if he wanted Linux and he said he had no idea show to navigate it (we advertised that we used Linux apache servers very early on).

The worst part is that isnt not the first time its happened.

We now have a larger tech test now to filter out all the chaff, and there is a lot.

Server deployment is not part of being a Fullstack developer, it’s part of DevOps.

@dsteiner totally, this fullstack shit is getting out of control, just include machine learning too FFS

The word, "fullstack," has been co-opted by programmers to make themselves sound more qualified than they really are. A fullstack engineer is a one-person IT department, and is typically compensated at about 1.5 to 3 times the rate of any normal employee. Somewhere in the last couple years, programmers who only know web technologies have taken the word, and applied it to the word developer, to create the meaningless term, "fullstack developer," to describe what literally every web developer should already have on his or her resume: frontend and backend knowledge.

The term has been diluted by this use and now has been reduced to just a meaningless buzzword.

@bahua This.
This is how the truth looks like.

So it seems like there are no agreements on what a fullstack developer should know, but we all seem to agree that a fullstack dev should know more than a few tools for than just one end of the stack. I wonder what is the minimum level of knowledge required for one to become a fullstack dev, and where should we draw the line?

I've worked on mobile apps, web and backend too but I stopped calling myself a fullstack dev because there's an ocean of tools, libraries, startegies, patterns and what not and I didn't think I knew enough of them. I would really like to know from some of the fullstack devs that commented, about their journey to the fullstack land.

@nrlhq

It's all nonsense. There's no acceptable threshold, because it doesn't mean anything. When I see a resume that says it, I usually pass, because it almost always means, "bullshit artist."

*watches in silence and not caring about titles*
Get the job done or get out, unless you are willing to learn.