E. W. Dijkstra proposed the dining philosophers problem in the early 1970s to showcase problems within concurrent programming. Nowadays, most programmers don’t happen to think about concurrency in programming when using languages like Golang or Python.

However, this oversight in how we write resilient software can lead us to upsetting security engineers, or dealing with ourselves being paged late into the night. Let’s revisit the dining philosophy problem, uncovering concurrency history - and leave with the foundational knowledge how to strengthen our systems against bad actors who use these foundations for evil.