I had the same problem in air travel industry. Our ticketing officers were never able to communicate how the ticket commission rules from our partners should be interpreted. I ended up adding a test framework, that allowed to add examples and counterexamples of existing flights to each rule, to verify that they are applied the way they'd assign commission by hand.
git's mental model is very, very small, if you care to learn it. Then all the commands and their "inconsistencies" start to make sense - they operate on the model almost without any magic, and not on whatever is user's intent (it can vary a lot)
I've tried to come up with the reason they don't do it, and thought MAYBE they were afraid people would put PINs for the cards there and they thought it's a bad idea. I wonder why I even tried to invent a good reason for them, designers could just lack perspective and do not care at all, even in apple.
give me ability to write a damn whatever on the card. My bank provides USD, EUR and other currencies on different cards with exact same cover. Maddening.
I can imagine that we don't have this option just because people would put their PINs there, and maybe it's not exactly secure enough, but sprinkle some validation on top and we'd be ok.
reply