Relearning How To Read
When I grow up I know what I want to be: Alive Most people become experts in their particular domain either by accident (they fell into expertise through...
- ios
- android
Originally published at rexstjohn.com on April 20, 2014. Recovered from the Internet Archive.
When I grow up I know what I want to be: Alive
Most people become experts in their particular domain either by accident (they fell into expertise through work) or through their own personal interests (they actively pursued a topic because it was fun). Still more gain expertise in school (which is often more general “expertise”).
Today, I am writing about a different kind of expert: The expert at becoming an expert…a person who is best exemplified by the cuddly mud skipper pictured above.
When such an individual observes that they are dwelling in a rapidly-drying expertise puddle in the desert, they will “skip” over the land to the next puddle (perhaps enduring months of discomfort)…to a much deeper, uninhabited puddle which no one else has yet found. Behind them, they will leave a pack of individuals who are arguing (with blue faces) that the puddle is not, in fact, dwindling because arguing is nearly always easier than changing.
In my experience, the primary mechanism for making these critical domain transitions efficiently is relearning how to read…
First, Some Context
High-tech is rough: technology changes so quickly you can pretty much set a 2 year “violent revolution” countdown clock. In the last 6 years alone we went from social to mobile to the “internet of things” as though the industry were on a schedule. Numerous industry-standard tools became technological “has-beens” (Flex or Silverlight anyone?), formerly valuable skill sets halved in value and dozens of companies imploded, unable to adapt with this rapid series of changes.
The winners, through all of this, were the ones who detected these waves early. For example, ngmoco was one of the first game companies to master mobile…they went from $40 million in funding to a $400 million exit in only two short years (2008-2010). It’s good to be an expert early.
Likewise, on an individual level, the rewards for becoming an “early adopter” of an ascending technology toolkit are vast: If you had immediately started programming Objective-C or Android in 2007 (the week after Steve Jobs raised the first iPhone), you could easily be sitting in a corner office at Square counting your millions of stock options along with your $200K base salary. The same goes for more recent technologies like Node.js and Unity3d…
Just like stocks, predicting the next killer skill and adapting rapidly has the potential to pay out massively.
Certified Domain Hopper
Some of the above may seem overly aggressive or harsh. A lot of it also easily falsifiable…there is plenty of evidence that certain tech skills have an extremely long shelf life (C or C++ much?). I suppose I have a different perspective on this issue, having completed a rather massive domain hop myself: I entered technology from a marketing background and then completely transitioned to software engineering.
If you have made a transition like this, you will understand that the “delta” between these two areas is large…marketing and writing software have literally nothing to do with one another and hardly anything I learned from one applied to the other (aside from maybe a math class or two). “Hop” or “Skip” fails to adequately describe it…it was a domain “Pole Vault.”
No one helped me make this transition. There was never a budget to train me or send me to school for more CS classes. It was all out of my own pocket…thousands of dollars worth of books on operating systems, compilers, programming languages and discrete mathematics. No one paid me for the nights and weekends I spent reading those books, carefully underlining them, building demo software, watching MIT lectures, writing tutorials and (more recently) giving talks….That time and those costs were all on me; I regret nothing because they were the best investment I have ever made.
Through it all I have learned one important lesson: Becoming an expert is a learnable skill.
The Skill of Becoming An Expert
Having made the initial leap from marketing to software, I had to optimize my somewhat shoddy existing study skills to a much greater degree…of all these optimizations, nothing has been more valuable then re-learning how to read.
When I get my hands on a technical book now, I read it as though I were studying for a final exam. I don’t just glance at the thing and kind of buzz through it…I attack it with a pen and scribble notes all over it. I underline the key parts, I write in the margins, I rephrase badly worded concepts and key sentences into my own language and dog-ear that book for weeks. If the book is long and boring, I skip through it and read the interesting or relevant parts and then return to the boring parts later after a good night of sleep. Then I reread the scribbles and underlines several times. If a section is confusing, I look up alternate explanations online…
By the time I am done with a given text, it is generally in an advanced state of decay…I greatly prefer physical books for this reason
Battle Textbook Bloat
Having purchased several used college textbooks I learned to become skeptical of bloated texts. Many college textbooks contain garbage passages or chapters which have been added for the sake of adding more material in order to sell new “updated” editions every year to college students. Realizing this, I learned to skip those chapters and concentrate on the critical parts. I’d rather read a high quality book about one topic than a bloated book which explores multiple topics in a half-assed manner.
A Book Compression Algorithm
On a per-passage basis, much of what is written in an average book is just filler or contextualizing babble which sets up key facts. If you were to remove all of this nonsense, you would be left with a significantly denser list of bullet points (which is exactly what most people arrive at when taking notes in class). Most books can be summarized in perhaps 25% of their overall size using bullet points without a tremendous loss in the information content. Learning to rapidly recognize what matters, underlining it and then rereading the book helps improve overall learning efficiency.
Identifying “Core Knowledge”
Every domain…Android, iOS, Computer Science…has a body of “Core Knowledge.” If you want to rapidly become an expert in a new domain, there are several methods for identifying what this “core knowledge” is:
- Search for lists of interview questions for “X” area, use them as a starting point
- Look at college curriculums for nearby universities and find what classes and textbooks they prescribe, go and buy cheap used versions from last year
- Talk to experts, ask them what books to read
The most important article I ever read was Steve Yegge’s “Get that job at Google.” It provided an excellent starting point for getting more in-depth with CS. Once you know what Core Knowledge is, you know how to proceed.
Technical Book Math & Estimation
The most recent book I have read is a 300 page, relatively technical text about the Bluetooth LE protocol. Reading semi-daily it has probably taken me about 1.5 weeks to eat my way through this thing. All told, I am guessing it is 2 weeks of energy to annotate, underline, re-read the important bits and review the concepts.
To become an “Expert” in a topic domain like iOS (which is a generally heavier set of tools to learn), you may need to read anywhere from 5-10 books (topic area examples: CoreData, XCode, Testing, Tools, 2-3 books on Objective-C, C-language, UIKit, several other related common frameworks, concurrency, etc), each about the same size as my Bluetooth LE book.
At a steady rate of consumption that may come out to around 5 months of research. That is in addition to working on projects during the day…this is a fairly aggressive timeline, most people might meander through this material over the course of several years.
Compiling A Study Guide
Over the years I have developed an “ultimate study guide” for iOS, Android, Cordova and Computer Science. It is now 18 pages long and contains extremely detailed bullet points on everything I believe is “core knowledge” that I must know.
Within these 18 pages is contained every important question I know I need to be able to answer for an average interview on these topics. It is extremely time efficient to keep such a guide handy because you know you are going to need it at some point…why reinvent the wheel? Why spend hours re-tracking down all this core knowledge?
Read it yourself: Ultimate Study Guide. I recommend writing your own study guides to meet your own needs…no one will write the exact guide for your particular field.
Compiling A Practice Guide
Software development also has a strong practice component…it is easy to get rusty on being able to cough up on-the-spot hand-written implementations of common algorithms and coding problems. To this end, I have also compiled what I call a “coding gym” which is basically something I can sit down and walk through, writing out problems on a paper pad sequentially.
Maybe there are people who can code in their sleep, I was never one of them…this gets me there if I do it for a week or so daily I have found. Brains are awfully magical things and sometimes need to be put through their paces.
Here is my “ProblemGuide” selection.
Knowledge Grazing
There are different levels of intensity you should think about. Not everything is an emergency…not everything is high pressure. Most of the time (90%) you should engage in very low-output preparation. This is the non-cramming aspect of becoming an expert…I call it “Knowledge Grazing.” I might have a YouTube lecture on some CS topic from MIT running while reading several technical websites and doing problems for a few hours. This isn’t really something I would do normally aside from a couple weeks away from being in an interview.
This kind of preparation is generally undirected…it is exploratory learning without an end goal. The idea is that you don’t actually know what you need to learn, just that you want to spend some time browsing around a particular topic to see what comes up.
One example might be to just read a Wikipedia article about a topic and then click into each link, read that article and then click into the links in those articles. You don’t really know where you are going…but it is good to get a handle on the scope of a particular domain.
Usually while doing this I tend to multi-task between several sources of information. Most lectures contain a lot of “dead air” (people writing on chalk boards etc) which would better be used reading an article or doing a problem. Learning to thread listening to an MIT lecture in with various other study activities helped me use my time more effectively.
Give a Talk
Nothing will motivate you to know what you are talking about like standing in front of 40 strangers, some of whom may be extreme advanced wizards at the topic you are speaking on. In preparation for my upcoming talk on Bluetooth LE I have found myself motivated to engage in significantly more advanced preparation than for even many interviews I have been on…
A rule of thumb I have heard others quote is that 1 slide takes 1 hour of preparation. I used to think that was a tad overkill but I know realize that 1 hour also includes the extensive reading, studying, memorization, fact checking and preparation components of what goes on that slide. Using that metric I have spent far more than 1 hour per slide on my next upcoming talk (50 slides).
Learn Something? Turn It Into A Guide
Whenever I encounter and annoying or difficult technical implementation problem, I have trained myself to attempt to convert that problem into a guide for others. There are a number of reasons for doing this…First, it helps me learn to force myself to write it all out. Second, it helps me drill into the facts more deeply so that I am sure I am not distributing false information. Third, it is fun to see others consuming the guides. I have written many guides at this point and seen traffic to my personal site rise from 20 hits a day to nearly 500 hits per day as a result…its good to know that other people are finding my writings useful.
Engineers Are Never Out Of School
The final thing I will leave off with is this: Engineers never leave school. For the reasons I have mentioned above, it is impossible to remain technical without engaging in significant ongoing study and preparation of some sort (unless you are just doing it for fun). Arnold Schwarzenegger once said “body building is not a sport, it is a lifestyle.” By that he meant that preparation pervades everything you do from how you sleep to how you eat, socialize and exercise. It requires 100% of your time to do it well. Technology is not different…your ongoing personal education isn’t a skill or habit: it is your life.