Gotta love software docs that show getting drunk on various amounts of vodka as an explanation of their select statement! This actually looks useful -- the sim

Gotta love software docs that show getting drunk on various amounts of vodka as an explanation of their select statement! This actually looks useful -- the simple set of rules they suggest make a lot of sense for general flowchart readability, and these could be easily shared with business partners of only a half-technical mindset. I was curious how you would handle event driven architectures with it, however -- or is that outside the intended scope?