That was a really good read. I appreciate the detail that the writer went into describing his investigative process.
Let the warning be heard loud and clear: state is the devil
Let the warning be heard loud and clear: state is the devil
Poorly managed state or ad hoc state machines are the devil. Once you model your system properly as a state machine, many of these issues fall out during the initial design and development (not to say they won't happen anyways, but this mitigates many of the issues). If you design your system so that whatever variables define your state are mutated together to ensure your invariants hold, this helps a lot with addressing poorly managed state. And if you can (you can't always) use a system which is aware of state machines as part of the design then you can mitigate the ad hoc state machine part.
Put differently, as long as you have good accountability of all the things that can change the state and are comfortable with how that set of things operates, then you are probably in a decent position.
> Posted by Natalie Silvanovich
but the bottom says
> Posted by Ryan
The latter is just the blogspot username though. It's quite scruffy.