People in this thread are generally telling you to either read a book or build something, when those things are not mutually exclusive. So read books, build th

People in this thread are generally telling you to either read a book or build something, when those things are not mutually exclusive. So read books, build things and read code. I like to dig into open source libraries/frameworks/tools that I use in my projects and try and understand their design. It would be great if the documentation people write focused a little on that, instead of the more common "this is how you install" and "this is how you use" (and sometimes "this is how you build it") - but writing docs is hard/tiring and so that knowledge gets lost.