In grade school, I discovered the power of testing what I knew, even at the risk of embarrassment. I was that kid who always had her hand raised in class—and I’d raise the other one when my hand got tired. Think Hermione without the restraint. (And often without the encyclopedic knowledge, but who’s counting?)
Later, after I caught on to the fact that the teacher wasn’t going to call me every time (even when mine was the only hand raised), I still kept doing it. I figured I might as well. After all, if other students didn’t want to take advantage of this part of the education that their tuition had already paid for, that was their loss. I wanted to see if I understood something well enough to explain it. (As a teacher, I winced slightly at recognizing my younger self in the eager hand-wavers who probably intimidated their classmates like all heck – but I sympathized, although I still prodded the quieter ones.)
There are no more teachers and no more exams, but I still share as much as I can. There’s a saying that goes, “Better to remain silent and be thought a fool than to speak and remove all doubt.” Me, I’d rather know when I’m being a fool. How can you find bugs in your code unless you look for them? How can you find flaws in your understanding unless you test what you think you know?
Duncan Mortimer saw the following similarities between sharing and test-driven development:
- Both provide you with tight feedback loops — the first person you’re sharing with when you write something up is yourself. I guess that’s a bit like getting a test to pass in TDD.
- Both help you to avoid ‘regressions’ — if you’ve got a permanent record of what you’ve done, what’s worked, what hasn’t, then perhaps it’s easier to get a sense for when an action you’re considering will cause problems.
- Both offer a form of ‘documentation’. Sharing, for your life: for your actions; for your situation. It shows what you were thinking at the time.
I like that. It’s why I blog. I get to find out whether I understand something enough to explain it, and if that explanation makes sense, and if I can answer the questions that other people might ask. I get a record that I can refer to and reminders of my fallability. Sharing helps me learn.
One of the tips that Timothy Kenny shares in Accelerated Learning for Entrepreneurs (e-book, $16.77) is assigning yourself a final project when you want to learn something well. Map the ideas, blog what you learn, create a checklist, write a report or a book, teach a class… create some kind of tangible proof that you’ve learned something. With that final project in mind, you’ll find—as Duncan also points out—that you study more deeply and more effectively.
Duncan wraps up with this thought:
Perhaps deliberately sharing your life and reflecting on that experience ultimately helps you to live a life that’s worth sharing?
… and I think there’s something to that. I’m learning a lot about life, and one of my ongoing projects is to have an amazing blog by the time I’m 60 or 90. That nudges me to learn things and do things that are worth sharing. It challenges me to share what I’m learning while I’m learning it, because later on the fuzziness of memory and the curse of expertise will make the details disappear.
How about you? What can you share, and how can sharing help you learn and live?Short URL: sach.ac/p/25617