.NET
The YouTube Channels Helping Me Learn C# and .NET
Tim Corey for fundamentals that actually stick, Nick Chapsas for what changed in the latest versions, and Balta plus Canal .NET in Portuguese. Four channels doing four different jobs.
A handful of channels do most of the work for me right now, each one covering a different part of learning C# and .NET, and none of them alone would get me all the way there.
Tim Corey for fundamentals
Tim Corey goes deep, which means his videos take real time to get through. A single course of his can run for hours instead of the twenty minutes most YouTube tutorials aim for.
That length is exactly what makes the fundamentals stick. Watching him build something from an empty project through to a finished, working piece of software, explaining every decision along the way, is a completely different experience from a fifteen-minute video that skips to the interesting part and leaves out why any of it works. When dependency injection finally made sense to me, it was because I'd watched someone wire it up from nothing rather than copy a line I couldn't explain.
Nick Chapsas for what's current
Nick Chapsas is where I go for the newer parts of .NET: performance details, language features, and the kind of changes between versions that don't show up in older tutorials or in answers still stuck on .NET 6.
C# moves fast enough that a tutorial from three years ago can teach a pattern the language has since replaced with something shorter and clearer. He is the correction for that, and I have picked up more than one habit from him that I now use without thinking about it.
Balta and Canal .NET in Portuguese
Balta is one of the best Brazilian channels for .NET, and I have built projects directly from his content: the CRUD app I wrote about earlier came straight out of one of his videos. Canal .NET covers similar ground, also in Portuguese.
That matters more than it sounds. Following code on screen while also translating an explanation in my head splits attention I would rather spend on the code itself. In my own language, one of those costs disappears.
Why four and not one
Between them I get fundamentals explained slowly, current .NET specifics, and content in my own language. Dropping to a single channel would lose one of those entirely.
The mix also stops me treating one person's habits as the only way to do something. When two of them solve the same problem differently, that difference is usually the part worth understanding, and it is the closest thing I get to a code review while learning on my own.