Expand Your Vision
Especially on social media, I see and read this preached a lot:
That’s a codswallop! Complete and utter 🐴💩.
And if you want to stay there for the rest of your career, that‘s totally okay. Just do this knowingly. Do it because you know that it is the right decision for you. Don’t do that because some figure with many followers on social media told you you should do it.
There is No Spoon
On top of all these, people who preach these things intentionally ignore that there is no such thing as “the stack”. The term “full-stack” is redundant at least, useless at worst.
The boundaries between the layers of “the stack” vanished a long time ago. It is a “mesh”—if anything—rather than a stack. Nowadays, the things one needs to know to manage an application end-to-end are so broad and wide that nobody can claim to know it all.
Think about it.
Can anyone claim to be an expert from Orchestration, to InfoSec, to performance optimization and SRE, to supply chain management, to Flexbox, to Edge networking and Serverless Compute, to CSS, sass and friends, to Accessibility and Usability, to Message Queues, Streams, Consensus Algorithms, Rate Limiting Distributed Tracing, to front end frameworks, to Databases, Sharding, Clustering, Distributed system design…?
☝️ The list can go on and on… No one on earth can assume to know the entire stack of things.
If one considers understanding the MERN Stack inside out as a sufficient prerequisite to adding the term “full-stack engineer” to their résumé, they likely don’t know how much they don’t know yet.
Is There Such Thing as a “Half-Stack” Anyway?
The curios thing is, there is no such thing as half-stack either.
To be a great software engineer, you’ll have to know both front-end and back-end anyway. Why? Because to be a great front-end developer, you first have to be a great back-end developer and vice versa. So if you think otherwise, you are deceiving yourself.
There Are No Boundaries
The stack is not layered. You cannot isolate the stack. Nor can you restrict the stack. Without knowing about one part of the stack, you cannot be productive in the other parts either.
Ergo, any qualified developer has no other choice to work across the stack. Calling a developer a “full-stack” developer is akin to calling a car a “horseless carriage”—It is redundant, outdated, and a tautology.
Know your path. Know where you want to go. And walk your path knowingly.
If you claim to work on the entire stack with a single language under your tool belt, it only proves that you are afraid of and closed to learning new things—None of these are good attributes to have in a developer who wants to get better at what they do.
Everything changes. And everything starts by knowing yourself.
Knowing one’s self, in itself, is a lifelong journey. A Twitter thread cannot show you that. Ironically, neither this article can show it to you. Though, I humbly hope it shed some light on the “why”s and “how” of expanding your horizon.
Until the next one… May the source be with you 🦄.
\ \\, \\\,^,.,,. “Zero to Hero” ,;7~((\))`;;,, <zerotohero.dev> ,(@') ;)`))\;;', stay up to date, be curious: learn ) . ),(( ))\;, /;`,,/7),)) )) )\,, (& )` (,((,((;( ))\,