Mythos Full-Stack Developer

“Full-Stack”

I always get very defensive when I hear or read that expression. "The stack" has grown much larger over the years - I've been building software since 1997 - and when someone claims to have mastered knowledge in all layers of "the stack" is no small claim.

Does that mean you have a large amount of knowledge, or are you specialized in every discipline?

The picture on the right shows a rough overview of what the individual layers in web development could mean. There is no information about the corresponding frameworks, and in my opinion this is where the myth and the falsification of perception start, because there are dozens of frameworks per layer. Also, the browser does not have to be the only client platform. See "Rich Client Platforms" of Eclipse or Adobe Flex.
At this point, thanks also to Andy Shora who wrote such an article almost four years ago. For me it was already coherent and therefore it was easy to translate it freely into German.

In the past there were less layers AND less frameworks per layer

Even in 2010 was a meaning of full stack has looked something like this. PHP, Python or Java Servlet, JavaScript (jQuery as highest of feelings), HTML, CSS and then via FTP to the live server. The server that hangs publicly on the Internet.
That was "Full-Stack". HTML looked quite trivial and the rest had more to do with "hobbyism".

My dislike is not directed against developers who have a lot of knowledge but against the term "Full-Stack".

From my point of view, what means "Full-Stack" today - 2016.
The number of layers has increased and the number of frameworks even disproportionately. Not to mention such libraries and frameworks - and these are often swept under the carpet - Google Analytics (for business data analysis), Test Frameworks or Crashlytics (for technical diagnostic data), Cloud Services and User Experience (UX).

The attached images exaggerate of course, but the amount of frameworks is there and they are used. The important information here - not all of the frameworks like each other at first sight and always need persuasion to work together.

Full-Stack 2010

Full-Stack 2016

Would I describe myself as „Full-Stack“ Developer?

When I started out - yes, maybe. Today I would rather call myself a backend developer with a good understanding of frontend technologies and user experience.
In my eyes it is much more important to learn new tools and skills. This is closely followed by the ability to know when to ask for advice, when you need a specialist and when you are at a loss.
Too many people hold themselves back just because they think they are already masters in something and don't want to learn more.

The wish and demand for a true master of „Full-Stacks“ – VERY HIGH

The chance of finding someone like that - very small.

Smaller companies, in my opinion, need at least someone who is at least roughly familiar with many areas, and new skills must be able to be acquired quickly if appropriate resources are not available.

Please tear me apart with your comments

I wait for the inevitable counterblow while I work on a piece of backend code for my aspired world domination. Limited by my insufficient knowledge of user experience.

War dieser Tipp hilfreich? Wenn ja, würde ich es sehr schätzen, wenn du einen Kommentar schreibst und den Post auf Facebook teilst.

Martin Zwigl

Martin's Blog - Computer & Technology