I did the same. In short examples like the ones used in the article, it's easy to reason about the states and transitions. But in a much larger codebase, it get

I did the same. In short examples like the ones used in the article, it's easy to reason about the states and transitions. But in a much larger codebase, it gets so much harder to even discover available transitions if one is leaning too much on the from/into implementations. Nice descriptive function names go a long way in terms of ergonomic coding.