This is the vibe I got as well. Which is fair enough (to each his/her own), but I thought I'd mention fast.ai which takes the opposite approach:
> Harvard professor David Perkins, who wrote Making Learning Whole (Jossey-Bass), has much to say about teaching. The basic idea is to teach the whole game. That means that if you're teaching baseball, you first take people to a baseball game or get them to play it. You don't teach them how to wind twine to make a baseball from scratch, the physics of a parabola, or the coefficient of friction of a ball on a bat.
Our perspective is the industrial one. And while there are certainly many complex business problems where deep learning is required, there are more cases where a traditional approach is sufficient and actually the better solution (e.g. due to the memory footprint, latency or other reasons). We routinely work on both kinds of problems on a day to day basis, but we would never go straight to deep learning approaches if simpler and faster traditional methods comprise a better solution in a given use case. So, our employees are expected to know both and to be able to judge when to apply which approach.
In a world of senseless marketing hype, I think it's a good idea to take the high road on this one. Reputation alone, even if less-buzzy words like ML are used in favor of AI, really carries a long ways. Plus, we're nearing the disenfranchisement hump, and AI's going to start taking a negative connotation with many businesses, I believe. Just shoot straight and I firmly believe it'll carry you for a long ways, there.
Yeah I get the same feeling. I am hesitant to suggest it, but gives a little bit of a gate-keeping vibe. Like only once you've payed sufficient homage to the same education path that I took, shall you be granted permission to be a 'real data scientist'.
That said, I think there is value in something like this more for hiring managers than practitioners... which makes sense considering the intro comments.
If I were to give a recommendation, it would be this -- pick a topic/project that interests you, follow the classic knowledge-bootstrapping process where you read through papers and (hopefully) have an expert or trained person walk you through the specifics, then get hands-on instantly. Especially with something like fast.ai that values empirical results over hard theory, something understandably popular in the field.
From there I'd recommend branching out, but I'd use a JIT approach. The field isn't necessarily super well-founded at the moment, and while machine learning fundamentals are useful, ultimately it's a waste of time compared to the long-tail benefit of getting immediate empirical results and feedback hands-on.
Just my 2c, YMMV, and anyone is totally welcome to disagree as they wish! :)
Best of luck,
T