Table of content
- Everyone wants to be called a fullstack developer
- The irony, the struggle and the risk
- Why not just be called a developer?
Everyone wants to be called a full stack developer.
In this blog, i will be talking about how being a full stack developer evolves and behaves. I always wonder momentarily and ask myself what all these developer titles really mean and its effects on how well people work.
I also had a hard time figuring out how one person could do a lot and still be called something of worth and even be paid measurably. Over the years, there hasn’t been a single moment where I have never questioned if one man could do it all.
There was a time I wondered if one person could have all the knowledge about software. People get the impression once they can code a bit of front-end and back-end, it makes them specialists in all fields of code.
Having spoken to a few professionals, it is a fallacy, a joke and requires some level of decorum to help survive in the nerdy world of 0s and 1s.
The irony, the struggle and the risk.
The whole farce about being a fullstack developer is like slippery slop, blind spot and needle in a hay stack to all the things that matter. Full stack development is said to be the combination of front-end, back-end and maybe devOps, cloud computing and data. That is where most people miss out on the point. DevOps is a new discovery in recent times.
A devop has basic knowledge of both IT development and software. Knowing how well everything operates and how to make products and software work to the satisfaction of the people involved both on the side of creation and usage.
These technologies come with loads of frameworks and tools. These include that of front-end, back-end and DevOps. Siting some examples of these tools and frameworks, js front end frameworks, .net blazor, HTML, CSS, PHP, Java, Laravel, C++, C#, Microsoft Azure DevOps etc.
All this in the mind of one man? Not a chance. I mean it is slightly possible but there could be a lot of short falls and challenges. Challenges which might include, limited time, new developments, opportunity to specialize and several others.
Why not just a “developer'' instead?
If there was a choice of which there is, I believe being called a developer with no extra appellation keeps things very open and teachable. There is always a thin line between being a Pro and a Beginner.
In a case where titles don’t dictate how well you perform, there is much more effort in performance which has been statistically proven on work ethics. In the end, the goal is to build awesome products as a developer.
Titles don’t prove whether or not you’re good, the work does.
Top comments (0)