I think it's a very good analogy. "What happens to control and data" between statements, expressions, and function calls is not taught in depth in a lot of undergraduate CS programs because it's usually handled automatically, and always one way. With monads, this stuff (which all falls under the rubric of composition) opens up to programmer control. So that's why I think the analogy is apt.