I don&#x27;t learn through reading a book, I can&#x27;t apply it to a scenario in my mind. I&#x27;ve tried.<p>I do learn through playing around with code and deconstructing existing code. There&#x27;s a crucial second step to this bit though - working out why it works. Without that, you&#x27;ve not really learned anything at all, you just know that if you poke it for a bit, it will eventually work.<p>People can get negative effects from tutorials, documentation, stack overflow too. Mainly where they see a piece of code that works, copy-paste it, tweak it a little and then leave it there.<p>I think the article is based around the wrong argument. The most important thing is working out how it works, not how you get to the stage of having code.<p>Edit: Not running code before committing and seeing that it works sounds horrible, is this a done thing? I feel it really shouldn&#x27;t be.