The most unconventional resource that levelled up my data science knowledge was reading academic papers on failed experiments. Not the polished, successful results you find in popular data science blogs - I mean the actual papers where researchers documented what went wrong, why their models did not perform as expected, and what they learned from the failure.
I stumbled onto this approach in 2020 when one of our developers at Software House was building a recommendation engine for an e-commerce client. We kept hitting accuracy problems that none of the standard tutorials or courses addressed. Out of frustration, I started searching for papers where similar models had underperformed, and that is where the real learning happened.
What makes failed experiment papers so valuable is that they reveal the messy reality of data science that courses deliberately skip over. A Coursera module will teach you how to build a random forest classifier with a clean dataset. A paper about a failed deployment will teach you what happens when your training data has a subtle seasonal bias that only shows up after three months in production. That second lesson is worth ten times more in practice.
I started a weekly habit of reading one paper from arXiv or similar repositories specifically looking for negative results or limitation discussions. Within about six months, my ability to anticipate problems in our data projects improved dramatically. I could look at a client's dataset and spot potential issues before we even started modelling because I had read about similar pitfalls in someone else's documented failure.
The reason this was more effective than courses or textbooks for me is that it developed judgment rather than just technical skill. Anyone can learn to write Python code for a neural network. Knowing when not to use one, or recognising that your data is too noisy for the approach you planned - that comes from studying what goes wrong, not just what goes right.