this post was submitted on 20 Aug 2026
18 points (95.0% liked)
Programming
28249 readers
282 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.