There's always a deeper stack, but I think for me it is a matter of how comfortable you are top to bottom with the parts which are not completely abstracted away from you. Also, just whether you are full stack within the expectations of your title.
As a web dev, I am full stack. And often that is what people are talking about. Typically the infra layers have been abstracted away from me. Maybe I can debug an infrastructure layer issue, but I can be full-stack without always worrying about that.
I think there's also room for "popular use" ultimately dictating things, as opposed to an overly literal determination, and I think it usually means client/server unless otherwise specified — where client can be a native UI or a web UI.
I think everyone should treat this as inherently fuzzy, at the end of the day.
Same category here. I call myself fullstack despite being fullstack in the web dev ecosystem. More accurately I like using ‘middle-stack’ for the interplay between backend and frontend logic in web applications, which is the core of my day job, but no one knows what that means.
French web developer mainly but touches everything. Volunteer mod here at DEV. I learn Nuxt at this moment and databases. — Addict to Cappuccino and Music
i've been saying 'middlestack' for a long time (as definite backend dev).
really, the full stack is huge. there's layout and design, ux, the huge realm of whatever js framework is the choice, then designing effective apis, being able to manage databases, and ops. it's not realistic to expect that one person can be sufficiently fluent in all those levels. designing an icon and configuring a reverse proxy are very different skillsets.
obviously, for smaller projects, a lot of that can be abstracted away with click-and-deliver solutions, but once you get above a certain scale, you really have to have people who focus on one end or the other.
of course, middlestack is still very valuable, even in larger operations. being able to have the flexibility to get things done in the api/ui range is important, even if you can't choose a colour palette or deal with the load balancer!
French web developer mainly but touches everything. Volunteer mod here at DEV. I learn Nuxt at this moment and databases. — Addict to Cappuccino and Music
There's always a deeper stack, but I think for me it is a matter of how comfortable you are top to bottom with the parts which are not completely abstracted away from you. Also, just whether you are full stack within the expectations of your title.
As a web dev, I am full stack. And often that is what people are talking about. Typically the infra layers have been abstracted away from me. Maybe I can debug an infrastructure layer issue, but I can be full-stack without always worrying about that.
I think there's also room for "popular use" ultimately dictating things, as opposed to an overly literal determination, and I think it usually means client/server unless otherwise specified — where client can be a native UI or a web UI.
I think everyone should treat this as inherently fuzzy, at the end of the day.
Same category here. I call myself fullstack despite being fullstack in the web dev ecosystem. More accurately I like using ‘middle-stack’ for the interplay between backend and frontend logic in web applications, which is the core of my day job, but no one knows what that means.
Oh! Pretty logic name middle-stack! Thanks!
i've been saying 'middlestack' for a long time (as definite backend dev).
really, the full stack is huge. there's layout and design, ux, the huge realm of whatever js framework is the choice, then designing effective apis, being able to manage databases, and ops. it's not realistic to expect that one person can be sufficiently fluent in all those levels. designing an icon and configuring a reverse proxy are very different skillsets.
obviously, for smaller projects, a lot of that can be abstracted away with click-and-deliver solutions, but once you get above a certain scale, you really have to have people who focus on one end or the other.
of course, middlestack is still very valuable, even in larger operations. being able to have the flexibility to get things done in the api/ui range is important, even if you can't choose a colour palette or deal with the load balancer!
Thanks Ben for your message!