How to learn a given technology at a deeper level? Part 1 — The “Why”

We’ll find the answer to the question posed in the heading, but first as Simon Sinek says, let’s first find out WHY to learn some specific technology at a deeper level? Because as a lot of experienced software engineers may have realised by now, that it is not necessary to learn ANY technology deeper than a level that is required in their day to day job. But in my opinion, there are still 2 reasons to learn:

1. Depth learning is required not to create a feature but to debug an existing feature, which most people outside of development think is easier than the former. So if you haven’t learned something in depth, then you may take more time to debug an issue, which according to some managers, might seem as if no progress is there. This sometimes makes us look bad in front of them.
2. Depth learning just gives the confidence all of us software developers so yearn for. Hopefully, it might deliver us from the chasms of “imposter syndrome”. Although, this reason may not apply to people who are naturally confident or have learned to be confident in the face of missing information.

In part 2, I’m going to cover the “how” part by illustrating how I learned java to the point that I can code any specified feature without sacrificing code quality and I can read any code to understand what it is trying to do.

Stay tuned for it.

Link to part 2

Link to part 3

P.S: If you think that this article has delivered great value to you, please support me by buying me a coffee.