Aim to fix classes of bugs

Fixing bugs in code often leads to increased complexity and the risk of introducing additional bugs due to the need to handle various edge cases, typically addressed with if statements. These conditions complicate the code, making it harder to understand and maintain, especially during refactoring, which can lead to regressions. An example from Rescale illustrates a bug in the local UI state handling for cloud-based desktop instances, where optimistic state updates could lead to confusing transitions for users. Instead of relying on additional if statements, a more robust solution was implemented by maintaining a set of statuses for each desktop and displaying the appropriate status based on the set's contents, eliminating any dependence on the order of status updates. This approach not only resolved the immediate issue but also addressed similar bugs, demonstrating the value of considering the broader class of problems when fixing bugs to avoid future complexity.