What, Why and How learning trick

We recently hired a DevOps intern at BeautifulCode. We gave him a learning plan which covers a lot of concepts in DevOps. In one of our one-one meetings, he raised a concern: “learning too many tools in a condensed period is putting pressure on me.” Firstly I agreed with him. Later I told him I would have felt the same way if I am in his position. Then I gave my 2 cents on the learning for which I haven’t prepared.

He had to learn 5 tools (I am calling tools, for lack of a better word). I have listed the tools in his learning plan and discussed What each tool does in the bigger picture.

  1. Terraform - to provision infrastructure
  2. Helm - to manage your Kubernetes resources
  3. Kubernetes - to manage your containers
  4. Cloud Build - CI/CD
  5. Ruby on Rails - framework to build web apps

Then we discussed the Why part. Why a particular tool over another, eg: you can replace Ruby on Rails with Django but the web concepts remain the same for the most part. Because both the frameworks are built on top of MVC architecture.

Once we know what a particular tool does the how is putting hours of learning and practicing.

After a few minutes, I have my Aha!! moment. I am capturing this for future reference. I am sure this is not the only trick available out there for learning, and this might be an old trick but I discovered it in my journey at this time.