The 70/30 rule
Posted on 2016-05-29 Edit on GitHub
I recently came across SimpleProgrammer.com, a blog by John Sonmez providing advice for working programmers on improving both their professional and non-professional lives. John also has a YouTube channel where he uploads videos with alarming regularity (multiple a day!), providing very actionable nuggets of wisdom.
One concept in particular resonated with me: the 70/30 rule. In short, the 70/30 rule is that we should:
Produce content 70% of the time, consume content 30% of the time.
"Producing" includes anything that creates value, while "consuming" is everything that doesn't produce value, including dedicated learning.
As John points out in another excellent video, How Do I Learn Complex and Big Programming Topics, the best way to learn is to start with a goal in mind, and learn enough to accomplish that goal.
At first, I found this idea difficult–how do I know what to set as the "right" goal? How do I know what is the "right" type of Android app to build, for example, if I don't read all I can about Android first? Shouldn't I consume as much as possible so I can make the "right" decisions when I produce?
As I've discovered over the past 1.5 years, and as John very quickly points out, trying to learn through consumption is inefficient. Your first app is going to be crap. So is the second. In fact, by actually building these apps, you're going to come into contact with more and more possibilities of what you could do, and will never be satisfied with what you've done. That's what true learning is about–getting in the thick of the action, not trying to become an expert by sitting on the sidelines.
I'm going to try to apply John's advice on the 70/30 rule. It'll be hard–I struggle to think of projects to do that interest me, whereas reading a book and doing some koans is easy, since someone else has already decided the format and structure for me. But, I've spent a lot of time trying to learn in an inefficient way, and something has to change.