Full stack developers are myth . Anyone who claims he is expert in both domains. He is lying. he would be implementing one side crappy solution and showing off that I developed everything from scratch. Tell him you are from monolithic era. You no longer exist. You are doing both side crappy solution go back to school and focus on one thing and come back with one thing which you can do properly

I'm a full stack developer. I like the idea of being a myth. It means I can ask for more money.

But those people will think you are a fraud

Experts are a myth.

Full stack just means you can build something from start to finish, front to back all on your own. That's it.

In some cases that might mean a lot... others very little.

It's not different than "I'm good with java"... That might mean a ton...or not.

The better rant is "full stack" doesn't mean "full stack", unless you also write browsers, network drivers, interpreters/compilers, etc

I believe in myself to become one.
All is left... to find how to make frontend.

Surely, nothing could go wrong, right?

Full-Stackers are just front-end developers who can make enough backend to make their front-end show stuff.

I only believe in beeing a full snack dev.

People making this argument totally miss the point of what makes a Dev good at their job. Tip - it's not being an expert in a technology!

I’m full stack.

UI. Console.
Business logic. Functions.
Data management. Pickle.

I did think about outsourcing the print statements, but I figured I have an eye for design, so why not go for it?

@sariel it just means you're lying 🙃

@iiii I don't think so. I may not be an expert in everything, but one thing I've learned in my years of experience.

Even the experts are full of shit.

I think what u actually mean is : senior full stack developers are a myth. I ve been working as a full stack developer for the past 4 years and becoming a senior is really hard. I ve seen only 1 true senior full atack dev in my carrer and the dude had like +10 years of experience.

@galacticus seniors realise how stupid being a full stack is and go for less full stack role. Most probably that is the case.

@iiii explain what your definition of a full stack developer is then.

I think it's important to know what your ideal candidate is.

@sariel I am no manager so I have no dream candidate, nor I am striving to be a manager

@iiii then I think it's ridiculous for you to argue that a full stack dev doesn't exist, especially since you can't put a definition to it.

@sariel I don't say it does not exist. Anyone can become a jack of all trades but a master of none. And that's exactly what full stack is. Understanding how things should interact is one thing, but actually developing the full stack is ridiculous.

@theabbie im the other way around. A server side focused dev who sometimes has to write frontend code/html/css as well as provision/ maintain cloud resources. I can get by on the frontend but its a much slower process for me than for someone more highly skilled on the frontend.

I agree though with the general sentiment that its hard and unusual for someone to be highly skilled in UI/UX design and implementation as well as the more logic focused backend work.

But honestly, a good dev should be able to shift gears and adapt to whats needed. A good javascript dev on the frontend is still a good dev and can learn the backend if needed. Likewise a good backend developer can get by on the frontend as long as everything looking like everybody else's work is ok (i.e. bootstrap all the things).

It just takes time and experience

Fair. I recently worked on a database project where I thought I'd do all of the frontend magic for that particular app. That didn't quite pan out.

Add I was taking a course specifically for databases... (which is fine, I did learn more SQL for my own good)

@iiii in my position I'm responsible for ensuring that my servers are provisioned, networking is configured correctly, compliance scans are taking place.

The OS must be configured correctly with all the right packages and libraries installed to host the application or database.

After that I deploy the stack and provide CICD to the server.

I'm capable of doing all that myself, however -- I rely on other teams to provide the support to rack the hardware, install the OS, provision the network, etc. Not because I cannot, but because my focus needs to be on the successful deployment of the application.

@sariel and that's exactly why I think that no one should be a full-stack. Everyone should focus on one specific thing rather than spreading out at several.

@iiii I think it takes both.

If everyone was hyper specialized progress would be slow and susceptible to failures.

By having a full stack dev in the mix helps alleviate those stress points and can streamline the entire process.

I may not know how one link in the chain works 100% but I doubt anyone can say that.

Mastery of a subject doesn't mean you know everything about it. To master a subject means you understand the rules that regulate it.

I think that's a misconception that needs to be challenged in our line of work. Nobody can know everything about a product unless they alone built it.

What @sariel said.

Even if I'm "pruning" my resume and removing all front end jobs I did. Not interested in front AT ALL, fuck you CSS.