One corollary about using positive space is that you realize we overuse booleans a lot. I routinely use a lot of boolean logic in my JavaScript and TypeScript c

One corollary about using positive space is that you realize we overuse booleans a lot. I routinely use a lot of boolean logic in my JavaScript and TypeScript code. I use it to decide when to display a component, when a component is being hovered, when it's odd, etc. Recently I wrote a simple tree walk interpreter and had to implement boolean unary negation: (UnaryOp::Not, Value::Bool(r)) => Ok(Value::Bool(!r)), Why is this line important? Well it's quite possibly the first[^1] time I have used the boolean negation (!) operation in Rust! Turns out, when you have proper enums, booleans aren't the best tool. Something like `isLoading` can now be `data LoadingState = Loading | Success`. Why is that better? Well if you want to add a third or fourth state, it's trivial. data LoadingState = Loading | Success | Failure You can even give it data to pass along data LoadingState a err = Loading | Success a | Failure err Turns out you can have a lot more states than two. Often times in the equivalent boolean case you end up with a couple booleans: isLoading, isError, etc. But then you end up with invalid boolean states! Like isLoading = true, isError = true. Huh? By making a multi-state type, you can restrict to only the possible states. [^1]: Meh actually more like 5th but you get my point