I'm all for consistency. But imagine having a codebase where most operations point back to an in-memory dataset representation of a database table, and everytim

I'm all for consistency. But imagine having a codebase where most operations point back to an in-memory dataset representation of a database table, and everytime you change your position in this dataset (the only "correct" way of accessing that table's data), it updates the UI accordingly. New feature where you compare 2 records ? Too bad, the UI is going to show them both then go back to the first one in a epileptic spasm. Sometimes, things are just that bad enough that keeping it consistent would mean producing things that will make clients call saying it's a bug. "No sorry, it's a feature actually".