I didn't do these particular courses but I found it a lot easier to stay motivated with the top down approach. First demonstrate usefulness, then deepen fundamentals.
When I was younger and didn't work full time + have other commitments the bottoms up approach appealed to me more, I think partially because I had bigger time blocks to allocate. i.e I could spend a whole weekend just learning fundamentals of some particular thing I was interested in and reach the first levels of usefulness in that one "session".
These days smaller time blocks mean that I need to walk away with something the keep the spark going for most curiosities.
Jeremy Howard came off as anti-intellectual to me. He is always like "oh math is nothing... you do not need math... math is not needed" and stuff like that.
Other than that, fast.ai is a great resource, and Jeremy Howard is a great instructor.
You will learn very practical tools and tricks, and a lot of recent research is demystified, but don't expect to achieve deep, general insights.
Also, fast.ai is a very very limited and poor library compared to PyTorch, JAX, TF, etc.
Programming, design, and architecture decisions are outright terrible.
I got paid to write fast.ai in one job. I still have nightmares. I never did it again.
I wouldn't say Jeremy is anti-intellectual, but he does know that a lot of people get turned off from the AI field because they are afraid of the math, and a lot of other courses (used to?) start with the math. So he makes sure early and often to tell people that you don't need to understand the math that is happening deep under the hood in order to do productive, even state-of-the-art, research with AI.
> When I was younger and didn't work full time + have other commitments
I second this - while both are great courses, I found I could only dedicate very short amounts of time recently to any kind of study, and going from the ground-up more thoroughly seemed like I was making no progress. The fast.ai top down approach worked a bit better for me for those reasons, otherwise it would have been interesting starting with the deep dive.
Yeah, this is probably the reason it worked better for me as well. I had bounced off of some other courses because I didn't have the time to dedicate 16+ hours of lectures before I would get to the fruit of all that foundational knowledge. Starting with some high-level abstractions, then digging down into how each of those abstractions ticked, kept the number of concepts I had to remember at once to something more manageable while dealing with distractions like a full-time job.
I did (old versions of) both of these and liked both. What I liked about the top-down approach of fast.ai is that it worked the way I approach working with other programming systems. You have a thing you want to do and APIs that promise to do that thing for you, and you plug them together. Then you decide you want to change it from the default behavior, so you tweak the parameters, then you need to learn why they're set up the way they are, and how they work, etc.
Similarly, when I learned web development with Rails over a decade ago, I didn't start by building an HTTP stack. I started by doing the build-a-blog-in-fifteen-minutes tutorial. Now I had a working project. Eventually I needed to learn all of the underlying technologies, but it's much easier and more rewarding to have something running first.
I found that starting with the big picture and a tangible result made it easier to stay engaged. At the end of the fastai course, however, I felt there were some gaps in my understanding especially at the low-level side. Andrew Ng's course helped fill in those gaps.
When I was younger and didn't work full time + have other commitments the bottoms up approach appealed to me more, I think partially because I had bigger time blocks to allocate. i.e I could spend a whole weekend just learning fundamentals of some particular thing I was interested in and reach the first levels of usefulness in that one "session".
These days smaller time blocks mean that I need to walk away with something the keep the spark going for most curiosities.