

I wouldn’t use SystemState for a boolean. Better to have Enable() or Disable().
The consideration is about what the consumer of that code knows about it. If it knows less about the inner workings and state, it has lower coupling. You can more easily change 1 without changing all the callers of it. Ideally code, especially in object oriented programming should have high cohesion (each class has one purpose and one reason for change) and low coupling.
Most stuff depends but those concepts can guide you. Learning SOLID principles helps to write better code.



Unless it is a rich Zimbabwean. Then it’s probably them. It’s about purchasing power and ability to buy air fare and cars etc.
It’s very easy to point at and blame others. We can all contribute to solving the problem.
If you can cycle rather than drive to work, the planet thanks you whether you’re in Michigan or Nairobi.