Reading docs is a skill. Reading docs is a skill.

In this post, I want to talk about the importance of developing your skills at reading technical documentations. During my first week at Bitmaker the instructors would tell me that you need to learn how to read code documentations because reading docs is a skill. Unfortunately, there are a lot of bad docs in this industry and you can’t really blame anyone because writing good docs is very hard. After all, coders are the ones that write them and they rather be coding! When I first started Bitmaker I would Google away my problems. Most of the times you’ll get an answer, but the quality of the answer could be questionable. And as a junior developer, recognizing the quality of code isn’t always obvious. Because of this, it’s best to go to the source first (the offical technical documentations), develop your own answer and then you’ll be in a better position to judge. There will be times where you can’t find the answer on Google, in these cases the docs is the next place you’ll have to look. So get good at it!

The more you practice, the faster you get at find answers in the docs. It’s especially important to read the documentations for the programming language you’re using. You learn so much more because you’ll often run across something you didn’t know while searching for a solution. So be patient! Take your time, and read carefully. Skills take time to develop, and you need practice to develop your skills. So practice reading docs! Because Reading docs is a skill!

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.