If someone were to call you a "full stack" developer, would that feel like a complement or an insult?

xia@lemmy.sdf.org to Asklemmy@lemmy.ml – 61 points –

I know managers love that term, but I think I've come to hear it as an insult... Sorta like being called an unprofessional "jack of all trades" budget handyman that does everything mediocre...

46

Nah, code is code. I've done a good chunk up and down the stack. DB specs, angular, no SQL, sql, react, jQuery, c#, node, infra, k8s, pho, java, blah blah blah

Fact of the matter is if you really want to be marketable you have to learn everything thrown at you, and usually fast. I say my number one skill is being able to pick up new tech, and recognizing where I need to learn more.

Not trying to sound arrogant, there is a ton I don't know, but to be employable now as an engineer you pretty much have to say yes when they ask if you know something, or prove you can learn it.

I was rejected for one job because I hadn't learned python fully.

Oh yeah but I can pick it up, probably before starting. I've done C++, C#, NodeJS, Go, Ruby, what's another language haha

" Sorry we really need someone who can code in python"

:| k well bye, guess it's just impossible to fathom that I could learn yet another scripting backend language. 15 years into my career I'm pretty sure I can just go learn another language now. If you bothered to test my skills at all you'd see in qualified, but sure. I learned it anyway just to spite them.

I was rejected for a role because I had experience with C++98, but they were developing exclusively in C++11. 🙄

Wow, too bad the Venn diagrams for those two are two completely separate unconnecting circles. I swear recruiters, just so freaking dumb

It wasn't the recruiter, it was the HM that made the decision. Dodged that bullet. The recruiter was great, we actually hung out some time after. He even bought me one of the devices I would have been working on and gave it to me after the interview, possibly as an attempt to butter me up, because he was excited about landing me.

that's fair, mine was a recruiter so I just assumed. Always frustrating that our careers hang in the balance of people who don't understand what we do

My current employer is run by highly technical people, and I know for a fact that the CTO is smarter than I am. It's refreshing.

Many languages today share so many common roots that if you know one you know enough of the others to get the ball rolling. I went from strictly front end to suddenly working in Python and PHP and similar languages. If you know the basics you know enough

it's very rare that I learn something that I can't pull some knowledge from somewhere else. I think moving to frontend was the largest leap as a whole, just that I'm not coding purely for efficiency and that things are reactive, where on servers most times you want to not be reactive. (Oversimplification). Overall yeah, code is code, every language and framework has it's quirks, but learning your first one is the hardest, second one is the biggest one that you realize how languages differ, and then after that it just gets easier. I haven't learned Go though... should probably do that at some point

My company has everything, but the titles are usually self-assigned.

Back end developers tend to write weird front end code, so their front end PRs usually need extra scrutiny.

Front end developers tend to write careless back end code, so their back end PRs usually need extra scrutiny.

I am a full stack developer, so all of my PRs need extra scrutiny.

Not an insult, just.... highly inaccurate. I can do everything from hardware, via databases, to coding against said databases. But for your sake, I hope you're not looking for UX/UI beyond (ab)using STDIO.

EDIT: What I cannot do is spelling, it seems.

That is a compliment. The separation of front end developer and back end developer is obsolete and untrue. Either you are a developer or not. If you work on web, then you must, now or in the future, know how web browsers work, how APIs work, how to write and consume them, etc. The browser is just an API we consume from JS. There are many others.

100% agree. Programming is programming, and these divisions are arbitrary and restrictive.

It'd be like if someone wanted to learn a language, but refused to learn vocabulary about an important topic.

I'm not going to write .Net, you can't make me do it. I'm not going to write Python, you can't make me do it.

Is your backend Node?!? Let's go baby, I'm a full stack dev.

Node and JS is just an example of how easy it is to write code for the back and front ends. You may employ as much langues as you want like PHP, Java, Rust, Python or even Elixir. Does not matter.

If you're not being sarcastic, why limit yourself to only one thing? If you're working on some amazing UI with tons of CSS animations and a full audiovisual experience, and it takes intimate knowledge of everything frontend, I guess it would make sense. But if you're just making internal CRUD apps, I don't see a reason why a given domain is special enough to have its own job title.

I agree that back end dev and front end JS are pretty much the same skillset, but HTML and CSS (especially so if you include design and UX) are very different and not something I would expect any dev to be able to pick up easily.

It's a compliment. Simply put, a senior full stack developer has leverage in their career's direction that a senior frontend or senior backend developer doesn't.

As a new dev who is still working on a "full-stack web dev" course. I would definitely take it as a compliment.

Can't say I would take it as either. Just means I'm qualified to work on the front- and back-end code at a professional level - no more no less.

I think it depends on the context. Calling me a full stack is an acknowledgement that I can work on every step of the system and usually every part of the system. I don't consider it to mean equally good.

However if it keeps getting brought up when I am not supposed to be working on those other steps, that signals to me that maybe they are trying to push more work into me that I shouldn't be do.

I can appreciate that when someone says "Our X Expert". It definitely feels like more praise and more value.

I couldn't imagine tying myself to a single category for my whole career.

I've done front end, back end, database, web, Windows, and Linux development. If the job calls for learning something new, I'm on it. These days I'm making datacenter software for admins to use to manage their distributed applications. Before this, I was doing the same thing for factory automation at the edge.

Specializing has its value, but the more flexible you can be, the more useful you will be when the landscape changes and your boss suddenly asks you to set up an AI system or something.

I think it's a complement. We're not in the dark ages anymore where you had to be intimately familiar with each target platform and have different people who each know everything about their little part of the stack. Nowadays it's feasible for one person to be productive in devops, database, backend, frontend, etc. because so many people have gone to great effort to get us there. I personally get a lot of enjoyment out of being able to stand up an app by myself without necessarily needing to work with six other teams. That way we can have an actual vision for an overall user experience rather than getting caught up in compatibilities and discussions of ever changing best practices.

Before I answer, I need to give some background. I've been in IT for past 20 years. I've been a backend developer, frontend developer, mobile developer, database administrator and most recently a devops engineer. I've got a degree in electronics and telecommunications and have had quite a bit of exposure to printed circuit board design, including processor programming. To answer your question, when someone refers to me as a "full stack" I don't take this as an insult. But it's diminishing.

Times have changed.

In the olden days, being 'full-stack' also involved memorizing resistor band colors and huffing solder fumes.

Kids these days.

Compliment. I love being able to do all the parts of modern software.

"Are you a full stack developer?"

"No, I specialize in ..."

I think every programmer should know how to write frontend and backend code, and how to deploy their code. Sure, everyone has their own specialization and things they like to do, but that doesn't mean they should be ignorant of all aspects of software development.

Well, personally, I'd be pretty peeved because my favorite focus is database shit - but in general I don't put much stock into titles unless they're being disbursed to justify forcing more work on me without compensation.

It depends on the context, who is saying it and why. If my manager is trying to say that after I've made it clear that I'm not interested in frontend development then it's insulting. Mostly because my manager isn't listening to me.

I'd assume they were trying to pimp me to some buzzwordoholic. I don't see any reasonable interpretation of it that's insulting, though.

Having it be (perceived as) the norm is absolutely stupid - but the issue is with ignorant management and recruiters, not people who get into entire stacks honestly for fun or profit.

I would assume you were misinformed and promptly point you to my previous JavaScript projects to dissuade you of such illusions.

It’s kind of meaningless - there’s only really development. If I was being brutally honest I do think a bit less of people who only work inside their one little niche of software, particularly if is just something like react, Salesforce or a CMS.

I understand most of the stack from photons to UX. I run optical, packet hardware and I define software. I consult on security and I inform the service desks. I'm that "break glass" guy you don't want to call in the middle if the night because I might be sarcastic, and then I'll cancel meetings for the next two days in revenge.

I've also been in this swamp since before the sky learned how to rain.

Call me whatever you want, but you'd best smile when you say it or I'll delete your account and blackhole your network.

/*clickety-click*

☝️ Just flexing.

"Full stack" is meant to be complimentary but is also highly situational, in the same way credentialed engineers and credentialed architects bristle when those.terms are used in the tech sector. They Did the Program, and Showed the Work. Those.of us in the tech sector are doing some stolen valor.by adopting those titles in our roles.

"Full stack" is situational because no two shops use the same stack. Every shop has its own technology preferences, so if you know Apache and ServiceNow, you'll still be useless in a shop that uses Xendesk and Nginx. It just.means you know YOUR venue's technology organization.

Really it's an industry buzz term, and you should run from any recruiters who casually use it but can't also describe exactly WHAT stack that shop they're pimping is using.