This article is a while bunch if strawman arguments if you ask me. Author's main point seems to be that state machines _can't_ know how they got to their curren

This article is a while bunch if strawman arguments if you ask me. Author's main point seems to be that state machines _can't_ know how they got to their current state and event driven systems will _always_ know how they arrived at their current state. But that's just nonsense. There is absolutely nothing intrinsic preventing a state machine knowing how it arrived at a state, in fact if you use an AWS state machine with lambda step functions you can look up any past execution of a state machine and see all the steps it took to arrive where it did. Furthermore, there's nothing intrinsic about event pipelines that makes them know all the actions taken up arrive somewhere. Not only that, but it's extremely common problem in large event architectures that teams and actions are so distributed you don't actually know who all your consumers are.