DEV Community

loading...

What is a Full-Stack Developer? A personal experience

tamouse profile image Tamara Temple ・5 min read

There's been some controversy about the term "Full Stack Developer" recently. There was this image floating around for a while:

drawing of a horse with a details back end and stick figure front end, labeled 'When there is 5 minutes to go on your test'. used to illustrate the discongruity of the term 'full-stack developer'. popularized in a tweet by @holtbt

I understand the concept. No one can be an expert in everything. No one should try. It makes sense to be deep in some area, and broad overall, but to expect any developer to be able to pick up anything on any given web app, software product, infrastructure project, etc, is a real management fallacy, and that is a problem if that's what your organization counts on.

How does that relate to me personally?

Well, at first I was offended.

Because I think I'm filling in the detail on the entire horse.

Except, of course, I'm not.

My work is very much front-end these days. I write a lot of React code, and need to understand the triumverate of web programming languages JavaScript, HTML, and CSS very well. I have about 10 years experience of writing Ruby, especially in Rails, but also as a general-purpose lanaguge. Developing web apps also requires understanding of system and shell languages, as well as understanding how databases work and the languages associated with them. My practice has included working as a business analyst, to uncover users' needs and translate them into actionable requirements for developers. I've worked in quality assurance, as an engineer, to develop processes that ensure customers and users get valuable and useful products. I've worked from deep in the guts of a unix kernel, writing device drivers, to the front of a dashboard control panel for network administration.

I am a generalist. But more important, I'm a problem solver. Sure, there's no way I can solve every problem, but I can pretty much understand problems well enough to find out who can solve it, and understand how it fits into the whole. So what does that make me?

I don't like the term "full-stack" -- it's too limiting.

While I'm writing a React component, I'm deeply interested in how the user experience of it manifests in solving a problem for the user interacting with it. What task are they hoping to accomplish, and am I writing the version of this component that's going to fulfill (part of) that task in the best way for the user?

While I'm writing that, am I going to be able to interact with our services and databases without taxing them or costing us more in infrastructure and/or support system nightmares?

In the specific area I work in, I'm using GraphQL, and there is no one else on the team who understands how to write a GraphQL API into our backend, so I do that as well.

So what does that make me? A unicorn? I don't know if it does. We have a small dev team (just enlarged by 2 people, but then diminished by losing our tech lead / manager); we all need to work all over the app. Some specialize in specific knowledge, but we also need to share knowledge of the product so it doesn't get lost and so people can review each other's work. I've spent the past couple years as the primary front-end dev without anyone to bounce ideas off of, or give solid review feedback; the team is super supportive, but mainly it's feedback like "Looks good to me!", "We trust you!", and so on; i.e., not constructive even if quite supportive. For the first 6 months, another team mate was also newly working on the mobile app; we couldn't even really give each other constructive feedback in that time. 2 years ago I wasn't working on the front-end at all. No question my breadth of experience over the years has let me make it through to here, but it hasn't been easy. So maybe this horse's front end is just a stick figure. But it won't stay that way.

I do think there is space in this world for generalists, but I don't think expecting such generalism to equate to being capable of all things anywhere in the product is doing anyone a service.

So what don't I do?

I'm rapidly losing touch with our operations stuff; I used to work a lot with chef, puppet, and ansible, working to provisioning servers and deploy software fully configured. I don't do that anymore, even necessarily with my own projects. Continuous Integration / Continuous Delivery is something I use, but it's not something I study anymore. There are lots of specific services the product integrates with that I know nothing about. Mobile development eludes me, and I just can't seem to get the hang of it. Anything to do with specific operating systems other than Unix-based ones remains somewhat opaque. (When I have to use XCode, I don't understand anything about what I'm looking at. I know a few buttons to push and that's all.)

I don't write any C code; I haven't for years. It used to be my everyday language for a decade, at least. Same for PHP and Perl. Ruby has replaced them all.

I still write Lisp, which was the 3rd language I ever learned, because, yay, emacs.

For most people starting out in their career, it's really great to focus in, get depth in a discipline. It's necessary to keep expanding beyond it, getting understanding of other disciplines, and there's more in common than not in many cases. Learning new languaqes, especially languages for different disciplines, is helpful. The tools to build software these days are pretty phenomenal, and also require study to use well. Even your code editor, whether it's vim/emacs, WebStorm, VSCode, Atom, or anything (requisite xkcd reference) requires studying how it works, how it can help you write better code, faster, and more accurately, and be customized or tailored to fit your "hand". (I'm an old emacser, and not a day goes by I'm not twiddling some setting or writing a snippet of elisp.)

If you label yourself a "Front-end Dev", or a "Back-end Dev", or a "Full-Stack Dev", that's absolutely great. I don't believe there's really a specific problem with labels; I think there can be problems when expectations are assumed because of the label, which is also inevitable. How important is how you label yourself to you? How long do you think you'll keep it?

Discussion (11)

pic
Editor guide
Collapse
elmuerte profile image
Michiel Hendriks

Don't label yourself on any side. You are a developer, one with preferences.

The term full stack is the worst. It will be used by PHBs to try to reduce cost and increase stress. A full stack developer will be tasked with doing the work of two, with only the time (and pay) for one.

Collapse
antonrich profile image
Anton

What is PHBs?

Collapse
tamouse profile image
Tamara Temple Author

"Pointy Haired Bosses" a reference to the character in the Dilbert comic strip.

example: assets.amuniversal.com/389f76b036d... - the person in the yellow shirt

In context: management types who think only in numbers without regard for people

Collapse
tamouse profile image
Tamara Temple Author

It will be used by PHBs to try to reduce cost and increase stress

Very much this. Thanks for this add, Michiel

Collapse
jorgecc profile image
Jorge Castro • Edited

IMHO, if you are a rook, then it's ok to specialize on something instead of being a Jack of All Trades (master of None). The front-end and the back-end are programmed in the same way. However, it shares different ideologies, they are used differently.

In a nutshell:

  • backend: CRUDL, forms, listing, maybe some dashboard and nothing else much. My pipeline is simple: database model + STC + some modifications and that's it

  • frontend: Way less interaction, maybe a few forms but nothing else much, the visual is highly important also SEO. Most of the job is about visualization rather interactivity. My pipeline is simple: buy a template (15 bucks) and join the template with the database. It's possible to create a front for a company in less than a week.

With experience, the rook could master both but its better to learn something right than to two half baked.

I do both and I'm pleased that most developers are clueless about SEO, they don't have an idea about how to do a proper front end. They do the technical stuff but nothing more. For example, the use of < h1 > is vital for SEO but most website don't use it correctly. However, some developers are specialist on front-end, and they know SEO correctly.

Collapse
mjjcha profile image
Judy Cha

Thanks for this awesome article, Tamara. I love being able to read the opinions of seasoned programmers. I'm pretty much of the same opinion as you - it doesn't matter what you label yourself, as long as you can deliver as advertised.

I used to keep the generic term "developer" for myself until more recently, when I started calling myself "fullstack". The big reason behind that was, non-devs have no idea what "developer" means. At meetups, I'd be asked what I do, and I would say that I write server side and client side code. "Oh, so you're fullstack?" Sure, why not.

I find that this is kinda like the concept of fight club - most devs quietly agree that the term "fullstack" is full of sh** but we let it slide, because the composition of web development is too vast for a layperson to understand.

Collapse
ivarojha profile image
Ravi Ojha • Edited

At this point in career, I like to label myself as full-stack. I was totally into backend at the start of the career. Then as I became more proficient at it, my efficiency of delivering backend increased by multiple folds. In an attempt to look for challenges, I dived into frontend and that was exciting too. By and by, as I time passed, I was able to manage with 40% time to backend and 60% to frontend for most features/stories.

How long do you think you'll keep it?

For future, I feel I need to strengthen dev-ops and security skills. That would truly justify the full-stack label. I think atleast for next 2 years this label makes sense for me.

Collapse
antonrich profile image
Anton

I'm trying to put a label on myself for a certain period of my time. However, I have a natural tendency to go into another direction. I have touched Elm, Elixir, Haskell, Vscode, Emacs, JavaSript, Bash. I really like it, though it feels overwhelming sometimes.

Collapse
diegomgar profile image
Dieg Oto

I consider myself full stack, but when i'm be asked about that, i always say that my strength is in backend, being a full stack and mastering front and back is simply a lie, everyone has a his preference and his strong.

And this is about my experience too, not only my opinion.

Collapse
mountainash profile image
Mountain/\Ash

Author: I don’t like to label myself, but when I do I use “a very seasoned software engineer”

Collapse
delueg profile image