lala_lala

Looks interesting. Like that the author modeled the failure scenario first before the correct one, it’s instructive. As other commenter pointed, a small typo in the title.

Yes, any analysis after an incident has the benefit, and bias, of hindsight.

But I see this post less as an incident analysis and more as an experiment in learning from hindsight. The goal, it seems, isn’t to replay what happened, but to show how formal methods let us model a complex system at a conceptual level, without access to every internal detail, and still reason about where races or inconsistencies could emerge.

As I read it, it felt more like an exploration from state space stand point (and not an example of model checking) which to me sounded quite reasonable. Unusual and intuitive I'd say.

Thanks for sharing. Is the code still running on Python 2.x or planning on transitioning to Python 3?

It is just that I have a job and a family to support. So I want to create something in whatever time I have. The prospect of engaging myself in myriad of courses sounds dull.

Maybe it's a folly but I am just intrigued by how they work and want to be able to develop them without committing to taking lot of courses.

Does it require any background in CS?