Learning about multi-threading mistakes

I don’t know if this will appeal to others besides maybe @Leo, but it’s an interesting way to learn about the risks posed by poorly design multi-threaded code in a friendly and approachable manner.

1 Like

dabbling in this area without having serious chops can bring on a world of hurt! reminds me of the time a java programmer thought he could do “c” code without being aware of what a memory leak is…