How my learning process work

It is known that when we want to start something new, something that we never had touch we are found a little bit lost. In my opinion, the worst part of this feeling is the overwhelming feeling that is always behind us, don’t let us continue our path, or what it would be the way to our new knowledge.

Photo by Windows on Unsplash

My first encounter with my target topic is something I heard of it, or the capabilities it can bring to my already started projects (this should be an abstract concept of it). This helps me a lot because it gives me keywords that help me with my research. I needed to give you this introduction because as soon as you start getting more information about the topic, more keywords you will get, and eventually they will make sense to help you build your final research.

For this example, let’s say I want to learn Kubernetes. My first researches should be to understand what is going on with my topic, its deep meaning. I would say that my first search would be “What is Kubernetes”, or just the word, to find the more basic information from Wikipedia.

Reading multiple options to our last question will bring us a general overview of what we are trying to find and the most important part: what we are trying to understand.

Our next step is really simple, we need to gather the technical information about it. For this I take different approaches, first of all, I try to take all technical data possible, for our example it would be YouTube tutorials, written tutorials, and documentation. I always go first to the documentation, to find how far I get without any help. In this step, I’ll find so many new keywords that in a step later will make sense to me. Technical details from the topic will result in a weird object for me until described further in the documentation on in a metaphor made by someone later.

Finding a tutorial, for my topic will help me to understand complex topics, a lot of these tutorials contain visuals that describe these kinds of elements. They can also include examples of ways that exemplify how the topic is applied to something bigger than the tutorial to get started. There are topics that I prefer to first hear all the tutorials to gather a great idea of what is going on. After that, I use the video as a dictionary while I try to replicate what I already “learned” or at least understood. At this point, your keywords will start to make a lot of sense and will start drawing a path of what you’ll need to start googling.

Keywords are like branches of the central topic, they help us to gather more information and also to become a real expert. Kubernetes (our example) might have keywords like “containers”, “pods”, “network”, “load balancer”. Each of these refers to something that is either about the technology itself or something that helps the technology to exists, an evolution of the same or the context of it. You’ll find where any of these descriptions fit after making their right research.

Photo by Sandy Millar on Unsplash

After this it’s just a matter of doing a lot of practical work with your topic, work with it and you’ll continue finding keywords and topics that will help you to gather knowledge. You can always replicate this cycle to the infinite with each new topic you find, even inside other topics. Extended sources like books will always help you to find the correct behavior, extends opinions and investigations about your topic, always read them to find those holes you feel in your knowledge.

This article at the end is how I learn, it might not work for you, or it might sound dumb to you. But at least I wanted to search how most of the things I know came to my mind.

Fullstack Developer. Inovation never ends. Seeking for a best future.