for many years "try to make code idempotent" was one of my most useful internal directives, and it seems like the one im thinking about the most now is "try to make error states unrepresentable"
Follow
@notplants Jokes aside, yeah, this is really good.
Comes with some UI problems though, like, how do you achieve that while still Interacting with the user / world and keeping them informed about why things happen
related: this blog post has some weird bits https://github.com/markqvist/Reticulum/blob/master/Zen%20of%20Reticulum.md
but I did appreciate their term "uncentralizable"
@forestjohnson totally. I have no aspiration to make all error states unrepresentable (the world is messy), but have found it an interesting guideline to try to make them unrepresentable where I can / within some particular subsystem