Everything. The state of YouTube content on ML is similar to what the state of software engineering <i>would</i> be if there were only videos on "Hello, world!" <i>or</i> conference talks about awesome products demoed on "Hello, world!" problems.<p>Practically none of the content creators seem to have ever executed a project that used ML, or worked in an ML team, and those who are doing that professionally don't do YouTube videos, except for talks in conferences that they <i>did</i> something, not really <i>how</i> they did it.<p>I think you are in a great position and can do a lot of good by showing how <i>you and your team</i> execute a project from <i>start</i> to <i>finish</i>.<p>Seasons and episodes. One season per project. One episode every week or two that addresses the problems solved, and how. I want to look at your screen and listen to conversations and brain-storming. How do you do ML, in long form videos from the field, not some bullshit 5 minutes videos with sentences like "then you only have to deploy your model". How do you collaborate on a project, how do you choose metrics that translate to the real world, how do you retrain your models, how do you do workload management, how do is your private cloud, do your ML practitioners have self service infra for training, how do you do self service deployment, manage data and access, how do you test data is not tainted, deploy and expose models, embed models.. How do you collaborate. How do you track knowledge, decisions, and assumptions and hypotheses.<p>For example, if you could take papers like <i>"The ML Test Score: A Rubric for ML Production Readiness and Technical Debt Reduction"</i>[^1] or <i>"Hidden Technical Debt in Machine Learning Systems"</i>[^2] and show how <i>your team</i> is dealing with each point, it would be great content.<p>All the thing that anyone who has spent a day in the real world knows isn't covered by 99% of the content online because the people doing it are either too busy, consider it competitive advantage, or don't know it even exists (had people working at FAANG try our internal platform, and they don't even deal with these problems because they're in "research" and they have teams of ops they can offload their notebook to).<p>[^1]: <a href="https://static.googleusercontent.com/media/research.google.com/en//pubs/archive/aad9f93b86b7addfea4c419b9100c6cdd26cacea.pdf" rel="nofollow">https://static.googleusercontent.com/media/research.google.c...</a><p>[^2]: <a href="https://papers.nips.cc/paper/5656-hidden-technical-debt-in-machine-learning-systems.pdf" rel="nofollow">https://papers.nips.cc/paper/5656-hidden-technical-debt-in-m...</a>