Future of Tech Education,
and Becoming Better at Anything
Nina walked up and asked if I worked for Code School.
She had missed a spot in Google Developers Women Techmakers sponsored Code School scholarships. She wondered if there were similar programs. She had obtained two undergrad degrees, but found her calling in developing software, and was seeking work.
“I talked to a lot of people about learning resources, and they told me ‘forget the rest, and just use Code School,’” Nina said to me.
‘Please connect with me. Our team will be in touch, and if we can help you learn to be a better developer and land a job, nothing would make us happier,’ I told her.
Nina and I had just listened to a San Francisco panel event featuring local tech education leaders, among them folks who work for Khan Academy, GitHub, or have founded organizations like Dev Bootcamp and Mission Bit. (Mission Bit provides free coding classes for public school students.)
What the Experts Say. Are They Right?
Jamie was also in the audience. I met Jamie a few weeks ago at an introductory JavaScript (JS) meetup featuring Code School JS content.
Jamie knew how to code, and had been a long-time Code School user (among other tools), but struggled to code consistently, and found it difficult to grow and find a job working as a programmer.
Among the panelists at this San Francisco event were Rachel Myers (GitHub and RailsBridge), Pamela Fox (Khan Academy and Girl Develop It), Tyson Daugherty (Mission Bit), and Jesse Farmer (Code Union).
Among the advice shared for someone like Jamie were to join a community, and to undertake a personal project, and learn by doing.
It is important to join a community, partly because it is difficult to stay accountable on one’s own. Yes, you can take the courses online, but so much of effective learning comes down to consistency and process. Some look to a community for process, or for consistency. Or both.
So much of what we learn is about exposure. Beyond the emotional support of those who are in the same boat, we want to be near where tips are changing hands on the latest and the greatest. It’s how we learn.
Another panelist pointed to the importance of projects.
“I made up exercises involving cats, but the intention wasn’t to have people tackle those exercises. I wanted them to produce something using something they cared about.”
Programming by Debugging and on Making Mistakes
Which is a great point. People often come to you looking for answers, when there are none!
We wish someone had the “keys” to questions like: ‘how do I learn to code?’ or ‘how can I get a job?’
As one of the panelists pointed out, the fault lies partly in how we are conditioned through the prevailing public education system. We are afraid of failing. We see mistakes as something negative. Rather than having the attitude of embracing (sometimes painful) failures as a path to growth, we shun mistakes and instead look for golden answers.
Get david kim’s stories in your inbox
Join Medium for free to get updates from this writer.
During that introductory JavaScript night, everyone kept looking at my projected screen as we walked through a for-loop example in the Chrome Browser console. I encouraged everyone to try it on their machines.
“Debugging is a great way to learn to program,” I said. I got blank stares.
I am sure that thought is shared by all who have learned to program. It is a point made by the Silicon Valley thought-leader and Y Combinator founder Paul Graham. In his famous essay “Hackers and Painters,” he wrote:
“I found that I liked to program sitting in front of a computer, not a piece of paper. Worse still, instead of patiently writing out a complete program and assuring myself it was correct, I tended to just spew out code that was hopelessly broken, and gradually beat it into shape. Debugging, I was taught, was a kind of final pass where you caught typos and oversights. The way I worked, it seemed like programming consisted of debugging.”
… the programming equivalent of a sculptor chipping away to craft a beautiful form from a formless block of stone.
But What About Jobs?
Many who came, came in the hopes of finding work as a software developer. In San Francisco’s tech community, people often refer to software engineers simply as “engineers,” as if all engineering were in software.
Someone in the audience asked “what do employers look for.”
Of course there are many practical tips, and many ideas were exchanged. I couldn’t stop but think to myself how important it is to invest in one’s skills, keep learning to be better, and not lose hope.
Naturally, certain tips will help during the job application process. For example, in tech interviews, one must have a strong command of algorithms and data structures (one panelist joked: “the answer to all algorithms questions is ‘hash tables!’”). For these, good books and interview resources exist (free algorithm challenges Project Euler is a popular alternative).
If algorithms and data structures form one pillar of a successful job interview, then another important pillar involves soft skills. People choose people they enjoy working with, or can have a beer with (the so-called ‘beer test’).
When confronted with difficult road block, one must learn how to get “unstuck.” One does that partly by realizing that an interview is not a solo effort. There are others in the room whom you can involve. How can you win the interviewer to you side? Will you have the peace of mind to say “I’m stuck, help me out here; let’s work together”?
Such a skill will not be learned over the course of an evening meetup.
Instead, it will take experience and many trials, some of which will feel like mistakes and failures.
Ice Cream and the Future of Education
Ask four developers how you should learn to be a better code; you will get four different answers. Some good, some bad.
And as we talked about the importance of community and of undertaking learning by doing, I was suddenly struck by how awesome Code School is as a technical learning resource. Code School has a very clear approach to teaching, and the mixed media of videos and exercises have been refined over the years, since the founder Gregg Pollack’s early days of tinkering with Rails for Zombies.
It works! And the people I talk to genuinely enjoy the experience of learning with Code School.
After the talk, and nearing 10 PM, some of us walked to a nearby burger joint called Super Duper, and kept talking about online education.
How can internet discussion interactions be improved? Based on the data from millions of users, are videos as effective as text?
What are some unexpected nuances of helping each other out on web forums or channels like Stack Overflow or IRC?
We all had interesting perspective to share on these questions, if we differed somewhat in our conclusions. What was clear is that we are at a very interesting and exciting time when it comes to learning! Web and mobile tools coupled with growing desire to invest in one’s skills (technical or otherwise) are both the masses and the teams dedicated to delivering education for the next decades.
Earlier in the day at Tech Crunch Disrupt Coursera co-founder, Daphne Koller, remarked that the third most popular course on Coursera was “Learning How to Learn.”
I hope Nina will continue to grow through her learning, and find a job as a developer. I would gladly pay for her Code School subscription. I wish there were a feature to give Code School as a gift.







