As you’ve probably noticed, the word “mastery” is often thrown around a lot at Launch School, but what does it actually mean?
So my cousin has a 1 1/2 year old toddler.
Last year when I met the little guy, he was struggling to walk. He was about 9 months at the time.
In this case, mastery is literally crawling before walking and walking before running. This kid is trying to crawl and watch his surroundings, he would only be able to stand up if he has something to support himself against such as a table or if one of us holds us hands so he can learn to use his legs.
Mastery is learning how to crawl and then once he’s very comfortable with that, he wants to get up and move around. Then as time passed on he had to master finding his balance if he was going to attempt to even walk. He’d fall over a couple times, but he would keep trying to get back up with his arms out to keep him balanced.
Once he mastered finding his balance, he was not only able to walk around but run around as well.
His next stage is trying to ride his tricycle, right now he doesn’t understand what pedaling is, so for now he gets off the tricycle and just pushes it by the handle bars.
So in this case, he needs to understand what pedaling with his feet is and then he will be able to ride the tricycle without getting off of it.
You might be asking, how is this applicable to programming. You have to learn to master the little details first before you can even attempt trying best practices and advanced tactics because you may not even get the most out of it and you might find yourself using these improperly.
It’s almost like my cousin trying to run when he can’t find his balance. The same thing can happen here.
Ideally you have to crawl before you walk, walk before you run.
Programming isn’t any different.