During the recent Web Application #DevDiscuss, the discussion of Full-Stack developers came up. From there, the discussion delved into the best ways to describe developers and their focus.
Max Antonucci@maxwell_devFull-stack developers are basically unicorns - they don't exist, and if they do then someone is playing a prank on you with a really bad costume. I think management people keep the myth alive to justify paying for fewer people. #DevDiscuss twitter.com/daveskull81/st…01:29 AM - 13 Mar 2019dAVE Inden @daveskull81The current state of web architecture shows how crazy the idea of being a “full stack” dev is getting nowadays. There’s so many layers to apps. It requires whole teams of people just to support dev environments and a build pipeline. #DevDiscuss
A lot of people felt they had an understanding of the entire stack, but were not extensively skilled across all of it. This led to the coining of the phrase, "Jack of the Stack". Eventually, the conversation turned to describing other developer types. The common concept of the "T" engineer was one of the first to be thrown out.
The developer who insists on CS purity over all else.
The developer who insists all sites should just use Bootstrap for the front-end.
The developer who doesn't want to learn anything else because C is where it all began for them.
The developer who posts constantly on DEV.
The developer that has general knowledge in a large number of areas, but also has a few areas where they have more depth of knowledge. This is a more realistic full stack developer definition.
The developer that writes their CSS inline, because F everything!
The developer that only talks about how much they hate other programming languages.
The developer ninja who wants to do everything themselves. The mythical 10x'er who probably causes more problems than they solve.
The developer that always insist on kicking the can down the road and solving the issue in a later PR.
The developer that rightly knows everything is about learning and is constantly trying to learn everything they can about all the things.
The developer that will not work on anything besides a Mac and they don’t understand why anyone uses Windows. Don’t get them started on Linux.
The developer with a singular focus on a particular stack to the point of recklessness. They want nothing to do with anything new.
The developer who is obsessed with all things O(n).
The developer that writes the cleanest code, complete with descriptive names, comments, and a fantastic README.
The developer that mostly circles around the same tech with one disturbing aberration.
The developer that thinks of the recursive solution to everything.
The developer that believes EVERYTHING needs a mixin!
The developer that has a lot of general knowledge, but is also an expert on one specific topic.
The master full-stack developer, which likely doesn't exist.
The developer who decides to throw all the code inline in the view so the HTML is a jumbled mess no one can read.
The developer that is constantly looking to work with the next shiny, new technology.
The developer who nitpicks the incorrect semantics of every single PR, thinking it must be eXactly on the mark before being merged.
The developer focused on accessibility. They're so important they should be earlier in the alphabet, and are so essential to each word, you almost think it should be a vowel.
The developer that has an obsession with an obscure language that no one knows about, yet they want everyone to learn. It is enough to put you to sleep.
The developer who can’t take their mind off of programming, and at the end of the day they forget lists, like sentences, don’t end in semicolons;
SO, which developer can you relate to?! If you can relate to multiple of them, you might just be a "Jack of the Stack!"
BIG Shoutout to my co-authors who helped come up with all these different devs! HIGHLY recommend giving each of them a follow! 🤗