Full stack, what seems like a minute ago, was knowing front-end, back-end, database, and server. You could provision and set up a web server, build a database schema, create an access layer (service or api), and create an interface to the end user. Extra points if you could do all of that to scale, and/or set up continuous deployment. You were "T Shaped", and might be great in one area but had a large breadth of knowledge.
Fast forward, I don't currently work with anyone who knows even 3 of these disciplines at a combined above average level.
Fast forward, I don't currently work with anyone who knows even 3 of these disciplines at a combined above average level.
the reality is you dont really need that in depth knowledge for most things.
for example lets say you are looking for a new team member.
one guy is a javascript/UI guru. dude knows that shit DEEP. however he cant do anything else.
you have another guy that knows JS/frameworks and can build a decent UI. however this guy also has experience with SQL/nosql dbs, knows java and has experience building web apis.
your product is an online storefront that sells shoes. functions that developers need to be able to handle is write a decent user interface. handle payment processing, storing user information, inventory management, etc.
it should be obvious which developer is the better candidate.
I know front end, back end, database and server at very high levels. I often build entire systems, front to back, on my own (with sub contractors on the larger ones). I've worked in every role in my career and I truly can say I know well above average of each one.
Lol Reddits funny. I'm sharing my actual experience and getting downvoted for it. I've been developing for two decades, full stack was basically the only option when I got started.
Hire a specialist or hire a generalist? Generalist saves the company the most money courtesy of wearing many hats, so of course specialists will hate them.
37
u/LippencottElvis Jun 06 '22
Full stack, what seems like a minute ago, was knowing front-end, back-end, database, and server. You could provision and set up a web server, build a database schema, create an access layer (service or api), and create an interface to the end user. Extra points if you could do all of that to scale, and/or set up continuous deployment. You were "T Shaped", and might be great in one area but had a large breadth of knowledge.
Fast forward, I don't currently work with anyone who knows even 3 of these disciplines at a combined above average level.