It may sound too bold, but:

\
I believe anyone with more than 8 or 10 years in web development can call themselves a "full-stack developer."

\
If they are passionate professionals, there is no chance of not having been involved in multiple personal or other projects where they are responsible for everything.

\
There is no chance they have never created a website for a friend or a relative.

\
There is no chance they haven't been seduced to make extra money with a side project, thus, creating a simple online shop or documentation by themselves.

\
The question is:

\
**Can we set a goal and leapfrog all these years of random experimentation or emergencies that grow us into multi-dimensional specialists?**

\
I think it's totally possible…

\
With a proper plan and focused effort, one can achieve it in a matter of months if they aren't a web development newbie.

\
But…

\
 ![](https://cdn.hackernoon.com/images/3FnIKHGgbNVQq1IJMsgvsFiWteK2-55a3ifs.jpeg)

## Why Should You Become A Full-Stack Engineer In The First Place

Because it's a perfect career move, especially if you feel bored or burned out, and by doing it, you enter an exciting new field with an unmatched variety of work!

\
For example, I spent the other week creating a browser extension. It's mostly for personal use, but I submitted it to Chrome's Web Store because - who knows - maybe other people will find it useful too.

\
Right after the submission, I talked about the extension on social media, and one of my contacts told me they also had an idea for one. So, I'm this close to getting a commercial project.

\
Plus, creating browser extensions turns out to be exciting for me…

\
And it's really refreshing.

\
I use the same old JavaScript, HTML, CSS, and React.js, but it feels like a new activity where you explore what's possible and how to achieve the best results.

\
It's amazing!

\
Switching between front-end and back-end tasks is refreshing, too. Both of them offer you unique challenges. So if you hit a dead end, you get a rest and work on something else.

\
There are many other reasons why it's worth it to be a full-stack javascript developer, but these are the most important ones I can think of now.

\
 ![](https://cdn.hackernoon.com/images/3FnIKHGgbNVQq1IJMsgvsFiWteK2-ecb3iut.jpeg)

## How You Become A Full-Stack JavaScript Developer

Well, that never happens overnight…

\
It's not like you decide and hop - you can now edit your LinkedIn profile and change your occupation.

\
It requires work…

\
And it requires time…

\
But if you want to make the transition as fast as humanly possible, then you can shorten the process by being strategic about how you spend your days.

\
Three main things that can help you are:

## **1. Focus on Full-Stack Technologies**

\
One shortcut is to learn some JavaScript frameworks and libraries that target full-stack developers. Using Next.Js or Remix is an excellent first step into this world.

\
If you're a front-end developer, you will be forced to think about things like containerization, APIs, DB storage, caching, and business logic of the application you build, but without some of the complexities of back-end development because these frameworks come with ready-to-use components.

\
If you're a back-end developer, you will be forced to think about pixel-perfect design, responsiveness, CSS&SCSS, API calls, component life-cycles, and more, but again - without some of the complexities because of the well-configured bundlers, linters, and other front-end components.

\
Such frameworks like Next.Js are the perfect introduction.

## **2. Launch a Side Project**

In my opinion, the best way to adopt new technologies is by combining learning with practicing. I can’t even remember the last time I read about something cool and didn't learn it by experimenting with it (a.k.a "Let's put it on my website and see what happens")

\
To learn Next.js, I created [BuhalBu.com](http://buhalbu.com/)…

\
To learn Tailwind CSS, I created a template named Darky…

\
To learn how to create browser extensions, I made [Code Aficionado](https://chrome.google.com/webstore/detail/code-aficionado/gbpmdppnfiaolojcamgmdpiacnchmlnj).

\
Every single time I adopted new technology, I made it by working on a side project.

\
Not that I've never learned anything new during work hours, but usually, you have a strictly defined stack there and not a lot of space for experimentation.

\
So if you want a stress-free and fun environment to become a full-stack dev, then you need to launch a side project.

## 3. Get an Entry-Level Job/Freelance Gigs

Well, sometimes that's hard to swallow it…

\
But why not get an entry-level job?

\
Basically, you will be paid to learn, and you will be able to invest all your time in this exciting endeavor. I guarantee you won't stay on that level for too long if you're a decent back-end or front-end dev.

\
Once you demonstrate confidence and start getting the new app's domain, you will be quickly promoted because you're not starting from scratch.

\
You already know stuff like the life-cycle of an HTTP request, how servers and browsers work, and much more general knowledge related to all web development.

## Conclusion

Some smart pants like to mock the full-stack devs, but often, the former are newcomers with just several years of experience.

\
They can't handle mentally how much time and effort is required...

\
Moreover, they believe web development was invented just before they got their first job.

\
Even worse…

\
Some are "old dogs" with a total lack of passion or ambition who never code after 5 o'clock.

\
I've never met a true, passionate web developer who isn't a multi-dimensional specialist interested in a wide variety of topics related to their job.

\
So, it's the JavaScript coder's destiny to adopt the full stack eventually.

Too Long; Didn't Read

Build an AI-based text classifier with Tensorflow & NoSQL

Why It's Your Destiny To Become A Full-Stack JavaScript Developer

Too Long; Didn't Read

@sashe

RELATED STORIES