I'd like to throw in the classic phrase: "just build something" in here.
I think, when it comes to learn new tools, the best approach to become proficient is, using them.
So to translate your own advice into DevOps:
To give an example from my own world if someone wanted to become a Data Analyst, saying just learn SQL is not quite true, don't bother learning how to do ETL, don't bother with views, and don't try to tackle PLSQL until much later.
I'd say:
Don't bother with Kubernetes, ServiceMeshes, and/or learning various cloud-provider APIs, trying to get something to "auto-scale".
I'd say, read up on Linux, VMs (containers), and pick one of the various automation tools and use them to set up a little pet-project (just a little VM maybe). Try to explore them and continue with the one you've felt most comfortable with.
And most importantly - Have fun.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think that is a very good starting point.
I'd like to throw in the classic phrase: "just build something" in here.
I think, when it comes to learn new tools, the best approach to become proficient is, using them.
So to translate your own advice into DevOps:
I'd say:
Don't bother with Kubernetes, ServiceMeshes, and/or learning various cloud-provider APIs, trying to get something to "auto-scale".
I'd say, read up on Linux, VMs (containers), and pick one of the various automation tools and use them to set up a little pet-project (just a little VM maybe). Try to explore them and continue with the one you've felt most comfortable with.
And most importantly - Have fun.