> most .NET programmers who I knew, would just hammer at things to make it work. I hope the examples you listed are facetious or from the very early days of as

> most .NET programmers who I knew, would just hammer at things to make it work. I hope the examples you listed are facetious or from the very early days of async/await in C#, otherwise I'd seriously question the skillset of the supposed .NET programmers. Visual Studio is fairly good at handling incorrect use of async/await, and in all of the examples you listed, the actual solution should've been "read the IDE error, hit the bulb and apply the automatically suggested fix", not "ignore the IDE error and smash keyboard until it works". ConfigureAwait usage is also not something you'll usually see outside of library code in modern C#.