The async/await State Machine can be easily understood with a comprehensive workflow diagram that models the program flow and the state transitions. Such a higher-level representation is a mandatory step before diving into the implementation

Dude you’ve been posting lots of good material! Now that I’m on holidays I have more time for reading, looking at the history of your blog I was slightly disappointed to see it only goes back to February – hopefully you’ll continue writing and posting good content for years to come.
I use state machines for programming robotics in c#, it is a great way to handle errors that will arise. I use the qf4net library, it is open source avail on Github.
I NEEDED THIS

!RemindMe 10 hours
I will be messaging you in 10 hours on 2020-12-13 08:33:09 UTC to remind you of this link
1 OTHERS CLICKED THIS LINK to send a PM to also be reminded and to reduce spam.
^{Parent commenter can delete this message to hide from others.}
A very “stupid” overview. I like it. It was very easy to understand, though it left a lot of questions for someone familiar with the level right below this – things like continuations and posting. You did say the next article would let us explore the implementation, so I’ll wait to see what that article covers before giving final judgement.
!RemindMe 30 hours
C# devs
null reference exceptions

source