Bonjour Thomas! It used to be that there were no "full-stack" developers as...there was no stack. Then PCs showed up and client-server was born (for big databases), then n-tier, then the design and code started to shift to OOD and OOP, then the middle-tier, buffer between font and back ends showed up quickly with quickly maturing communication conduits (XML, EDI, SOAP, XML-RPC, REST, and lately a front/middle tier, GraphQL). Backends also grew from linked-list, to RMS, to SQL, to Document Management (Mongo, NoSQL, etc). Front ends blew up with web apps and the myriad of NPM-delivered packages necessary to build them. Self-contained (what one person in this thread called "archaic") languages (like Java and C#) matured to support better principals like GoF but also became more complex with the easy-to-consume NuGet packages.
So...front, middle, and backend stacks have become more powerful and more complex to the point where it's difficult for one to be called "full-stack" without qualifying one as "a jack of all stacks, master of none". Though, I've always coached jr or mid-level devs to truly master one and getting a productive working knowledge of the other two. Because..."if all you have is a hammer...". :)
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
Bonjour Thomas! It used to be that there were no "full-stack" developers as...there was no stack. Then PCs showed up and client-server was born (for big databases), then n-tier, then the design and code started to shift to OOD and OOP, then the middle-tier, buffer between font and back ends showed up quickly with quickly maturing communication conduits (XML, EDI, SOAP, XML-RPC, REST, and lately a front/middle tier, GraphQL). Backends also grew from linked-list, to RMS, to SQL, to Document Management (Mongo, NoSQL, etc). Front ends blew up with web apps and the myriad of NPM-delivered packages necessary to build them. Self-contained (what one person in this thread called "archaic") languages (like Java and C#) matured to support better principals like GoF but also became more complex with the easy-to-consume NuGet packages.
So...front, middle, and backend stacks have become more powerful and more complex to the point where it's difficult for one to be called "full-stack" without qualifying one as "a jack of all stacks, master of none". Though, I've always coached jr or mid-level devs to truly master one and getting a productive working knowledge of the other two. Because..."if all you have is a hammer...". :)
Thanks for your explanation!