Cervantes once wrote that "the journey is better than the inn", but I rather like to think that the journey is the inn.

It means that irrespective to its difficulties (and likely because of them), your adventures is what you look back on with fondness at its end rather than the end itself. It's why I enjoy reading "The Lord of the Rings" every five years or so, where as I age and experience the hand life has dealt me, I find myself appreciating different aspects of the story and gaining new insights into what I value and into what I want to be as a human being. I find my journey with deep learning to be roughly analgous to that.

I've been a part of the fast.ai community for several years. I've been through the course multiple times (since it was using theano back in the old days), I've contributed to the library, and use it as the basis for one of my own. And as with each course, a re-reading of the book brings new insights, ideas, and revelations.

And so here I begin with my meandering thoughts and reflections from yet another reading of what I consider "The Lord of the Rings" of deep learning. As such, it makes sense to being with the most foundational topic in fastbook, "How do you learn Deep Learning?"

You can do this!

Hi, everybody; I'm Jeremy ... I do not have any formal technical education ... didn't have great grades. I was much more interested in doing real projects. 1

This is meaningful to me as someone with a BA in History and a MA in Theology. It's a reminder that if you want something, it's within your grasp to make it happen if you are willing to put in the work. It's also a reminder that key to getting there is actually doing something! If find too many people thinking that if they just get into that school, or if they can just take that class, then they'll be a good software enginner or deep learning practitioner. The reality is that the only way you get there is by doing it ... just like pull-ups (which aren't much fun when you're starting out and/or you're 49 and overweight).

The problem with traditional education

... how math is taught - we require students to spend years doing rote memorization and learning dry disconnected fundatmentals that we claim will pay off later, long after most of them quit the subject. 2

This also is the problem with higher education in general, where young people spend at least four to five years learning things they already learned in High School or else things they don't really care about and will be forgotten right after finals, spending in excess of $100,000 for the privilege of it and likely going into debt in the tens of thousands of dollars, all with this idea that having done it they will be prepared for the real world. Unfortunately, that's not how it works. Whether you are in a university of even go to university, what matter is what you do ... not what classes you took or what your GPA is.

Deep Learning (and coding in general) is an art maybe more so than a science

The hardest part of deep learning is artisanal. 3

I remember going to an iOS conference way back in the day and a conference speaker asking how many folks in the session I was sitting in had a background in music. 80-90% of the audience raised their hands. Sure, there is math and stats and a science to deep learning, but like any coding enterprise, it's an art ... with some artists being better than others along with room for improvement regardless of whether you're Van Gough or painting by the numbers.

Doing is how you learn, and what you've done is what matters

... focus on your hobbies and passions ... Common character traits in the people who do well at deep learning include playfulness and curiosity. 4

at Tesla .. CEO Elon Musk says 'A PhD is definitely not required. All that matters is a deep understanding of AI & ability to implement NNs in a way that is actually useful .... Don't care if you even graduated High School.' 5

... the most important thing for learning deep learning is writing code and experimenting." 6

Folks to follow

It's always helpful to have some role models; folks who practice the lessons learned above and can help you along your journey.

For starters, consider this image of the top 12 users based on most likes in the fast.ai forums:

Aside from the founders of fast.ai and a bunch of them working for noteable ML companies like Hugging Face and Weights & Biases, I can think of at least FOUR things these folks have in common:

  1. They are fearless in asking what they may have even considered, dumb questions.

  2. They are active in researching the answers to their own questions (even the dumb ones) and those asked by others.

  3. They are active in teaching others through blogs, books, open source libraries, study groups, and podcasts.

  4. They build things! That is, they all have experience building models and making them usable via deployed applications and/or in kaggle compeititions. Anyone can bake a half-cooked model in a Jupyter notebook, but few can turn it into something others can use.

These traits aren't just key to learning deep learning; they are key to learning anything! Practice them and you guarantee yourself success in learning anything you've set your mind on.

What if I can only follow three?

Aside from Jeremy (@jeremyphoward), who's a given, if I could only follow three people who have mastered to art of learning deep learning, they would be ...

Radek Osmulsk: (twitter: @radekosmulski)

Zach Mueller: (twitter: @TheZachMueller)

Sanyam Bhutani: (twitter: @bhutanisanyam1)

Personally, I do follow each of these individuals on twitter and you should too! Though I've never met any of them IRL, I consider the colleagues, friends, and amongst the most helpful for those looking to get started in machine learning.

Tip: Twitter is imo the best place to network with fellow ML/DL practioners and stay up-to-date with the latest developments in ML in general

What if I'm too lazy to read any of that stuff above?

Well, you can watch this video (and then go back and read that stuff anyways) ...

1. "Chaper 1: Your Deep Learning Journey". In The Fastbook p.8

2. Ibid., p.9

3. Ibid., p.10

4. Ibid., p.11

5. Ibid.

6. Ibid.