This is how I learn 100s of DevOps tools in less time | 3 step strategy.

Summary

In this video, Abishek shares his personal approach to learning new DevOps tools, which can be overwhelming due to the multitude of options available. He suggests starting with understanding 'why' a tool exists, then 'what' it does, and finally 'how' it operates. Using Kubernetes as an example, he explains how to grasp its necessity, its features, and its implementation. This method helps in learning not just one tool but adapting to many, making the process less daunting and more efficient.

Takeaways

• 😎 The speaker, Abishek, shares his personal approach to learning new tools in DevOps, emphasizing the importance of understanding the 'why,' 'what,' and 'how' of a technology.
• 🤔 He suggests starting with the 'why' to grasp the necessity and challenges a tool addresses, using Kubernetes as an example to explain its rise in popularity due to virtualization issues.
• 📚 Abishek recommends exploring the problems with existing technologies before moving to the new tool, which helps in understanding the motivation behind the tool's creation.
• 💡 The 'what' phase involves understanding the features and functionalities of the tool, focusing on the basics before diving into advanced concepts.
• 🛠️ He advises hands-on practice with basic functionalities to solidify understanding before moving onto more complex features.
• 🔧 The 'how' phase is tool-specific, focusing on the implementation details and architecture unique to each technology.
• 🌟 Abishek highlights that the 'why' and 'what' aspects remain consistent across tools, while the 'how' aspect varies, which is where most of the learning effort is needed.
• 🚀 By mastering the 'why' and 'what,' the learning curve for new tools becomes less steep, allowing for faster adoption of new technologies.
• 📈 He suggests that this approach not only aids in learning but also helps in interviews, as fundamentals are often more critical than advanced concepts.
• 💬 Abishek invites feedback and encourages viewers to try this approach, emphasizing its effectiveness in his own learning journey.

Q & A

What is the main challenge Abishek addresses in his video?

Abishek addresses the challenge of learning a vast number of tools in DevOps, which can be overwhelming for beginners.

What is Abishek's personal approach to learning new tools in DevOps?

Abishek's approach involves understanding 'why', 'what', and 'how' a tool is used before diving into its technical details.

Why does Abishek emphasize starting with 'why' when learning a new technology?

Starting with 'why' helps Abishek understand the problem a technology solves, its relevance, and its historical context, which provides a strong foundation for learning.

What does Abishek suggest doing after understanding the 'why' of a technology?

After understanding 'why', Abishek suggests focusing on 'what', which involves learning about the features and functionalities of the technology.

How does Abishek approach the 'how' aspect of learning a new tool?

Abishek approaches 'how' by understanding the specific implementation details of the tool, such as its architecture or unique features, which can vary between tools.

What example does Abishek use to illustrate his learning approach?

Abishek uses Kubernetes as an example to illustrate his approach, starting from understanding virtualization and containerization to learning Kubernetes' role in solving problems associated with these technologies.

Why does Abishek recommend focusing more time on the 'why' aspect when learning new technologies?

Focusing on 'why' strengthens the fundamental understanding of a technology, making it easier to adapt to new tools and technologies in the future.

What is the benefit of Abishek's approach when transitioning between different DevOps tools?

Abishek's approach allows for a faster learning curve when moving between tools because the 'why' and 'what' aspects remain consistent, only the 'how' aspect changes.

How does Abishek's approach help in understanding complex features like pods in Kubernetes?

Understanding the 'why' behind Kubernetes, such as the ephemeral nature of containers and service discovery issues, makes complex features like pods more comprehensible.

What advice does Abishek give for those who find learning multiple DevOps tools overwhelming?

Abishek advises trying his 'why', 'what', and 'how' approach and focusing more time on the 'why' aspect to build a strong foundation and reduce the feeling of being overwhelmed.