[🔥 Learn ML for beginners 🥳] I recently said I'll be binge-watching fast.ai's Practical Deep Learning for Coders and I did, here are my final thoughts!
I'm mainly going to contrast it with @coursera's course as that's the course I took back in late 2018.
1/
Verdict:
If you're in high school or a student or more precisely somebody who still has difficulties creating your own learning program (no experience with self-education) I'd recommend you take @coursera's course - it's more streamlined.
2/
You'll know exactly when to read, watch, or code.
On the other hand, if you already have some experience (you had some tech internships/jobs) or you're considering switching careers (again you're experienced) or simply integrating deep learning into your own domain...
3/
I recommend you take fast.ai's course. A track record in learning on your own is preferable for this route!
Why?
https://t.co/Tv0gvOs3JD's course requires more self-discipline and organization (time management, make your own program...) compared to @coursera.
4/
After the first lecture, you'll need to go through the Jupyter, start Colab or a GPU server, play with code a bit, search through the docs, etc. All on your own. Whereas @coursera's platform forces you to do these steps, you just keep clicking and doing your tasks.
5/
This makes complete sense - @jeremyphoward (@fastdotai course lecturer) is very proficient with self-learning (learned Chinese on his own, programming, etc.) - so much that I'm afraid that he underestimates how much guidance some people actually need, IMHO.
6/
Example: The part on p-value (lecture 2) may be very very overwhelming for beginners. Be comfortable with not understanding everything if you take the course.
fast.ai's course pros:
* Using PyTorch + fastai (wrapper lib around PyTorch) instead of TF + Keras.
7/
* They give many great tips around learning (like sharing the stuff you learn via blogging to improve recall/strengthen your personal brand). Coursera's course doesn't put much focus on this - and I think it's vital.
* Great teaching methodology using a top-down approach.
8/
Also, I love the fact they're always using a running (usually highly visual) example.
fast.ai's course cons:
* Requires some experience with self-learning (arguably not a con but this may be a feature to consider when you're picking the right course for you).
9/
* Missing heroes of deep learning lectures that Coursera had.
* It'd be nice if they covered transformers and not RNNs/LSTMs in the last lecture (lecture 8). Although I understand covering these older fundamental models has its value.
10/
Let me know your thoughts?
I guess I'm in a unique position here as not many people went through both courses (or at least skimmed them for a couple of days).
The original LinkedIn post for reference (contains summaries and various notes and tips): linkedin.com/posts/aleksago…
11/
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Again thanks to @PetarV_93, @relja_work, Cameron Anderson, Saima Hussain for being supportive throughout this journey!
2/
In this blog you'll find:
* The details on how @DeepMind's hiring pipeline is structured.
* Many tips on how to prepare for top-tier AI labs (like DeepMind, OpenAI, etc.) in the world (for research engineering roles but I guess many tips will apply for scientists as well).
3/
I'll be binge-watching @jeremyphoward and @GuggerSylvain's @fastdotai "Practical Deep Learning for Coders" course today and tomorrow! 8 lectures, ~2h each. It's going to be fun! 😂 Why?
Well:
1/
* I want to update my blog on getting started with ML from 2019 where I only recommended @coursera (and I realized just how bad my writing was just 2.5 years ago!).
I recommend you bookmark it but don't read it just yet, it should be ready by the end of this week!
* I want to be able to give better advice to "younger folks" in general. I get a lot of questions on my Discord as well (join it if you haven't: discord.gg/peBrCpheKE).
3/
* The problem of catastrophic forgetting (babies face it - that's (probably) why you don't have any memories of when you were really young - and AIs face it). How do we go about cracking it?
2/
* Embodied AI - does an "AI" have to have a body before it is actually intelligent? It seems our body is a distributed processing system.
As an example, they mention the shape of the ear canal and the fact it does some form of Fourier analysis in real-time ...
3/
Why do people care that much about being 1st on @kaggle?
What is the main motivation to compete there?
If you're trying to help people/learn a lot/get hired here is an alternative (way less competitive): build a useful and original ML project, open-source it, and maintain it.
@kaggle reminds me of the competitive programming world a lot.
Up to a certain point, the skills you acquire are super useful.
After that point, you start missing out on everything else it takes to be a good engineer/researcher or whatever it is you're trying to accomplish.
While you're learning shortcuts for std::vector::push_back, increasing your typing speed and some variations of the algorithms you already know, other people are learning how to design software that is maintainable, collaborate with other people, present their work, etc.