Here’s the new personal development project I’m starting this week:
Starting with Why:
I am deeply fascinated with the BitcoinSV network and the implications it has for the future of commerce and information exchange. There are many interesting articles, videos, podcasts, and rabbit trails I enjoy pursuing, but I continue to run up against roadblocks created by so many technical things that go over my head. By putting forth the effort to grasp the conceptual foundations of computer science, I hope to partially alleviate that problem.
Additionally, I am very intrigued by other subjects like Systems Thinking, Networking Theory, Knowledge Management, Information Theory, etc. At some point, I need to stop gazing longingly at these topics as distant subjects that I dream of understanding some day. I need to just pick an accessible starting point, dive in, and build on those understandings over time.
I am not studying computer science because I have been convinced that it’s “important” or “necessary” nor am I studying it because I’m under some illusion that I will emerge as the world’s best coder. I am a relentless servant to my curiosity here. And while I acknowledge the possibility that ensuing knowledge/skill could pay off in some sort of pragmatic way, my primary agenda is to have a lot more fun in my Bitcoin research and in my exploration of unfamiliar mental models that can make me a better thinker.
There are two Richard P. Feynman quotes that capture the spirit of my efforts here:
“Physics is like sex: sure, it may give some practical results, but that’s not why we do it.”
“Study hard what interests you the most in the most undisciplined, irreverent and original manner possible.”
So my approach to learning these things may take many “irresponsible” and “impractical” twists and turns depending where my curiosity leads me. For those who study these things because they would like to get a coding job, my approach will likely not bear the markings of a “man on a mission.”
TLDR: “I’m just trying to nerd out, bro.”
What’s the Agenda:
Here are the two books I’m reading to begin with:
I’m going to devote 30-minutes to each book every morning while I have my AM cup of coffee. My hope is that I will be able to move through a chapter per week for each book. The chapters are relatively short, but also dense. Each book builds from the ground up beginning with very basic things dealing with the core function of computers, the distinction between software/hardware, the key topics/terms in the field overall, etc. Things get more technical as you proceed step by step, so my pace may slow down as I go. Achieving a “sexy” goal like “completing a book a week” is not what’s important to me here. I truly want to internalize my understanding and grasp what I learn in a way that’s substantive. So I will move as slowly as I need to understand whatever topic I’m on. I’m already planning on supplementing my studies with YouTube videos that delve deeper into any topics I struggle with. The two books I have chose seem to have a very well-structured table of content, a simple writing style, and a very sequential process that will be critical for someone with no technical background.
TLDR: 10 minutes of coding per day, 1 hour of reading per day
Learning Out Loud:
As I make my way through these books, I’ll spend roughly 10-15 minutes per day capturing my understandings, questions, and musings on Evernote. At the end of the week, I’ll do a video summary where I explain what I learned. For me, it’s much harder to fake your understandings when you have to talk about them, so this is a way to help me really ensure I’m getting it. It’s easy for me to read and “think” I understand until I have to actually summarize it and illustrate it.
This process of learning out loud is partially for accountability (ie. it keeps me on my toes to know I have someone who might be watching) and partially for reinforcing the ideas (ie. You retain more when you have to do something with what you’re learning).
I plan on doing this M-F and using my weekends to reflect on my results and refine my approach. Weekends will be a time for me to step back from the details and see what’s working (and not working).
TLDR: One written summary per day, One video summary per week
How long does this last: