The Only Advice You Need To Become a Developer

Lots of wrong advice is being handed out here by people who have never actually been developers or failed to become one or people who are just bad developers.

The technologies do not define a developer/programmer.

A programmer is a problem solver. A programmer is not a person limited by his tools, it is a person who is willing to put in the work and learn the tools needed to do the job.
Good programmers ask questions, best programmers ask things to be explained to them like they are idiots.
Why you may ask? It is very simple.
Distilled information coming from people with expertise is better consumed.
I see people being afraid to ask questions and what is worse is then there are people who answer these questions in a very condescending way and if you are that type of person, fuck you. No, seriously.

For the people who constantly ask "wHaT iS tHe BeSt CoUrSe To LeArN XYZ", you guys are making your life VERY DIFFICULT.

"So what do I do?" - you might be asking yourself, and the answer to that is VERY SIMPLE.

GO READ OFFICIAL DOCUMENTATION

This will not only teach you how to navigate technical documentation, but it will teach you self-reliance and it will give you the confidence to tackle unknowns.
Can't make sense of the docs? Read again. Can't make sense of the docs again? Go watch porn, watch Netflix, chill out a bit, and then come back. Still cannot understand? Read again, write down with actual words what you think you understand and what you need help with and go to forums and ask for help. But, the thing you should be doing is not asking for the best course to watch or some other resource where you expect knowledge to be spoon-fed to you.

Here is a short story.

I had the pleasure to work with a Junior Developer a few years ago. He was around 60.
Turns out he was a programmer in the early 70/80's. How did he become one you ask?
All the dude had was one book and a crap computer without internet.
He told me that he read the book like 20 times before it clicked, took him like 3-4 months.
There was no internet back then, nobody to ask.
He said, once it clicked, everything fell into place and he started building games, later on, he joined a software company, and afterward he made his own company which he ran for like 30 years, and sold it.
You may ask why did he want to continue development and I asked him that as well.
The guy was loaded with money, I could tell so it wasn't for the money.
He said solving problems is what he wants to do and for him, it's a quest for knowledge.

What is the moral of the story?
The moral of the story is that the initiative starts with you and you shouldn't rely on anything else.
If you do not commit to understanding what you are trying to do, you will be forever stuck in watching videos and asking for help and what tech stack is best.

This is it, the is the only thing you need.
You need to trust yourself and give yourself the time to understand a given technology.
You need to work hard until it clicks, once this happens, everything afterward is like a waterfall.
Rinse and repeat.

Every time we build software at work (and we build software for a lot of money), we fail our way to production. We break pipelines, introduce bugs all the time. It happens and no process in this world will prevent that. Nothing is perfect and it will never be. But we iterate and we make it better. And after each iteration, broken pipelines and bugs diminish.

The same stupid principle applies here.

You know you want to learn something. Take small steps and iterate. Trust yourself.

This is the only advice I give to every Junior developer or people who want to become developers and I hope this opens the eyes for some of you. It is that simple.