async/await common mistakes I keep seeing in production_

Task.Run is for CPU-bound work. Wrapping a synchronous I/O call in Task.Run does not make it truly async — you just burn a thread pool thread while waiting. Use truly async APIs: HttpClient, EF Core async methods, Stream.ReadAsync, and so on.

The most common async bug I see is calling .Result or .Wait() on a Task inside an async method running on a synchronization context. This deadlocks 100% of the time in ASP.NET Framework and WinForms. Always use await instead.

Pinning Stephen Cleary's blog series on async as required reading for this thread. It is the definitive guide on not blocking on async code in C#.

async void methods cannot be awaited, so exceptions thrown inside them crash the process. The only valid use case is event handlers. Use async Task everywhere else. I have personally seen this take down a production service.