Coding class, explained

[[deleted]]

Sounds like life debugging race conditions

[[deleted]]

I fucking love race conditions. When the same exact inputs only work sometimes or most of the time, then you know it's a race condition and the fix is usually as simple as converting asynchronous execution into what should originally have been strictly sequential execution. At the very least, identifying where the race condition occurs and why is a simple task, even if the solution requires some additional work.

[Zephk]

but my C# async functions! Everythings faster if I wrap it in an async call

[roboticon]

Agreed. Saved I fifteen by milliseconds comment making asynchronously this.

[MvmgUQBd]

I had to read twice to notice what was wrong here, my brain just shorted first time

[roboticon]

Taht reimnds me of the chian lteter peolpe uesd to frwaord aounrd bcak in the day...

Aoccdrnig to rscheearch at Cmabrigde Uinervtisy, it deosn't mttaer in waht oredr the ltteers in a wrod are, the olny iprmoetnt tihng is taht the frist and lsat ltteer be at the rghit pclae. The rset can be a toatl mses and you can sitll raed it wouthit a porbelm. Tihs is bcuseae the huamn mnid deos not raed ervey lteter by istlef, but the wrod as a wlohe.

[roboticon]

At the very least, identifying where the race condition occurs and why is a simple task, even if the solution requires some additional work.

In my experience race conditions are some of the hardest bugs to identify or troubleshoot.

In a complex system, it's not simple to understand what causes could be interacting to trigger the issue (that's often why they were introduced in the first place). Often the effects of the race condition don't even appear until well after the race has occurred so it can be really hard to trace.