Ⅱ - Learn how to learn #

Nobody learns (effectively) by being shown what to do. You can watch hundreds of hours of people playing guitar, even explaining how they do it, but you won’t be able to randomly pick one up and play if you never have before.

Furthermore, as much as you can learn from direct reading and instruction, it has its place and limits. This guide, book, whatever you want to call it, was never meant to be followed like instructions. You should go out on your own and poke around, get lost in the weeds as you go. If you find a topic dull, don’t read it as in depth. I don’t want you wasting your time.

Break things. Make mistakes.

By the end of this, you should know what a burning resistor smells like, what it’s like to try to recover from a Linux system that just won’t boot, and how it feels when a bug has been eluding you for hours and your code still doesn’t work.

The only way that happens is if you try ideas when you get them and do more than what’s in this guide. So, please, if you find a topic interesting, don’t make this website you’re one stop shop - go surf the web.

Failing is part of learning and proof that you’re doing well.

These experiences should teach you things in their own right. The smell of burning electronics may help you diagnose a future circuit, the lesson to not fall into a pit of technical debt may help when a bug has engulfed your code, and the late night of terminal only based work as you try to get your computer working again will teach you more than this book ever can.

To quote someone much smarter than myself→

You should also constantly be looking for how to break, modify, or look into how things work. For example, try right-clicking on this sentence and select Inspect, like this:


You should see a <p hidden> element, try editing it to remove the word hidden, then the text from that element should appear above this. (this sometimes doesn’t work correctly right away, so you might have to right-click and inspect twice, but then you should see the HTML source for this section of the page)

But try to take this lesson elsewhere, try renaming a .docx (word) file to a .zip and extracting it, or looking through the ventilation of your electronics to see if you can see what makes them tick, whatever. Curiosity is my primary incentive to learn, and often taking a peek into the innards of electronics or code or machines can reveal a lot.

If you’re looking for some more advice, see this page, literally titled “Advice”

Other Resources #

How To Learn Stuff Quickly (Josh W Comeau)

Use Google like a pro

Learn about problems, not solutions (Gareth Dwyer)

How to learn things at 1000x the speed (Pranay Prakash)

My Engineering Axioms (Martin Rue’s Blog)

xkcd №2501

If you would like to support my development of OpGuides, please consider supporting me on GitHub Sponsors or dropping me some spare change on Venmo @vegadeftwing - every little bit helps ❤️