This should also make it clear that anything else you read in this article is inherently opinion.

There’s no way to measure if one person is more of a fullstack engineer than someone else.The only consensus regarding fullstack is that nobody agrees what it is. There is no scientific model that describes what fullstack is. That’s because, fullstack engineering isn’t a real thing. If you have criticisms about this definition, good. From initial user experience to backend code running on distributed servers.” “Individual responsible for engineering the end-to-end features of a system.

Let’s start with a generic, definitely-not-controversial definition of a fullstack engineer: Over the last year of teaching myself webdev, I’ve encountered many myths and learned a lot of things about fullstack development. If there’s one thing that nobody in the developer ecosystem can agree on, it’s what constitutes a fullstack engineer. I fully support the notion of a fullstack engineer who has never written a line of HTML or CSS, they are simply not the focus of this article. I also want to explicitly disclaim that I will be focusing on fullstack in a web development context. I suspect that a lot of people will interpret this article as “gatekeeping.” Although I can understand that perspective, I’ve strived to provide an honest outlook that reflects my experience over the last few years (mostly startups). If you disagree, drop a comment and let us know your take-respectfully, of course. The opinions expressed here are solely those of the author. This is the first in an ongoing series from developers expressing their opinions on various topics in the software engineering and computer science world.

Imho the best app builder