I think the `switch` pattern is only applicable when you're checking for a large number of configurations that are of boolean type - ie. isReadOnly, isAdmin, isUser, isSuperUser, hasPaid, isActivated, isBanned, etc - it basically depends on your use case, unusual pattern to use, but it has its merits if applied in the right time by the right developer

case isReadOnly: // change something;

case isAdmin: doAdminStuff();

case hasPaid: updateFinance();

case isActivated: updatedUserInfo();

and so on...