Full-stacks do not exist
Introduction
I am in the IT industry for quite a long time and somewhere on the line, the idea emerges that full-stacks do not exist — and I was always really skeptical about this idea. I believe I have plenty of arguments to defend this hypothesis. Of course, this will be my personal opinion on the topic, but with a solid background and maybe with a bit of luck this article will trigger some discussion and will help me to understand the other side — which will be: Full-stacks actually do exist.
What does it mean to be full-stack?
First of all, we should start with a definition of what full-stack is. In my opinion, full-stack is a developer who understands multiple stacks, the level of the understanding will be somewhere around the expert level. The definition of a stack will be simpler: backend — means that developer knows languages, tools, and frameworks on the level that allows him to deliver server applications. A more concrete example here would be a python, django, django-rest-framework or python, sanic. Of course — in the backend areas we also expect a developer to know database systems on the level that allows him to comfortably model the data structure and do most of the maintenance tasks — for example, database migrations and replication. The same applies to the frontend stack — javascript, react and…
