Cheers!

Before writing that post I was thinking about focusing more on the process of learning, and the way I find learning programming somewhat different to learning many other skills. For programming often allows and even encourages learning by experimenting - you write something, run it to see what it does, then you alter something and run it again, and that way you discover what you can do and how the code works. And in case the code doesn't work (which happens often), usually the worst you get is an error message, or a blank screen. I don't know, but somehow I'd imagine it might be a bit different with learning chemistry or high-voltage electric installations - if your experiment fails, you might get an explosion or some other severe real-world consequences.

Or, with skills like carpentry and building - some of that I've also learned by doing and with some trial and error. But sometimes it is a bit frustrating, like when I did my first major masonry work together with a friend - we had almost zero experience with masonry, but we decided to try anyhow. Only when we got the project half-way done we realized that if we had did some things differently in the very bottom layers things would've been easier for us in the latter part of the work. But when we learned that it was already too late - we didn't feel like tearing apart the whole thing and starting over. But with coding all of this is often easier - we can copy&paste blocks of code, rearrange and re-write stuff rather easily (especially with the modern IDEs which offer powerful search&replace and re-factor tools).