>So it's a way of imperatively declaring execution sequence dependencies that lets you reason as if there's only pure functions most of the time. No. Monad is

>So it's a way of imperatively declaring execution sequence dependencies that lets you reason as if there's only pure functions most of the time. No. Monad is just a “design pattern”. It’s nice that this design pattern happens to be useful to force sequential evaluation, but it’s just one of the many things that fits the monad abstraction.