Overwhelmed by what should I learn?

[shivajikobardan]

My job is a LinuxAdmin where I require Linux and SQL. I am currently doing RHCSA course and SQL course. But I've purchased DCA and CKA(Docker and Kubernetes Certification courses) as well because I got them on discount (I'm not doing certification, just doing course to learn)

At the same moment, I want to learn programming because that's my ultimate aim, to be able to program. For that I have a C++ exercises book by walter savitch and Javascript projects course by Laurence Svekis(Which I'm planning to buy).

I want to learn about nginx, jenkins, aws, terraform, bash scripting, tomcat, apache, RHCE, github, ccna, selenium, promethus etc.

I also want to create my own blog website about a topic unrelated to these any.

How do I plan? How do I manage my plan?

[brudgers]

nginx, jenkins, aws, terraform, bash scripting, tomcat, apache, RHCE, github, ccna, selenium, promethus etc

Most of these are things that make sense in a job where they make sense.

Of them bash scripting is the only one likely to directly improve your daily life.

Maybe Github...or rather Git might help you organize text files.

The rest are knowledge domains that are better when sharded across a team so that individuals can show each other how they work. They are mostly bigger than one person can really learn...how big is AWS? AWS includes semi-trailers full of hard disks that will come to a data-center and make a physical copy of data, satellite networks, and items of similar scale.

And Kubernetes? its basic design was expected to be run by teams of Google engineers. Not one person with a laptop. Kubernetes is meant not for you.

Bash scripting, SQL, Javascript, and Emacs/Vim are things that you can take with you and will always matter at any scale.

Good luck.

[austin-cheney]

You have analysis paralysis. Stop thinking about what decisions you should make. Instead build something ambitious. That thing you build will dictate what you need to learn.

[codegladiator]

There are two parts

1. How things are made: This is your programming language/core concepts/DSA/Problem solving. Don't start with two languages. Start with 1 along with design/psds/algo.

2. Why things are made: These are the tools like nginx/jenkins/aws/terraform etc. Understand their purpose. Think of how you would have solved the problem (#1), and then go in depth one by one into their detail.

If you are not using what you learn regularly, then you will quite easily forget it. So mix 1 and 2 to keep things interesting.

As for blogging, start taking private notes first. Eventually you will have a note detailed enough for someone else to read. Then you start to blog.

[skadamat]

Have you thought about mastering the meta-skill of learning a topic area somewhat deeply, before moving on to something else? Normally, I would say "go for it! interleave the things you want to learn" but I wonder if your excitement for learning lots of things is hindering your learning?

It could be a form of procrastination :)

[baremetal]

If I was you I would start with javascript and worry about the rest of the stuff later.

Learn things as you need them, to achieve specific goals.