My problem is mainly when, because of sofware, database (or anything related to IT) architecture impose its way into how the real world works.
For example, imagine Deutsche Telekom. If you have a contract for both mobile phone and internet at home with them, it's completely reasonable that they have different internal systems and thus your name is stored in different locations.
Let's say you change your name. You call Deutsche Telekom (mobile) and tell them that you changed your name, the lady tells you that she updated your name in the computer and all is good. Next month you get the invoice and it shows your old name.
My question is: is this acceptable?
From one perspective, you could say that yes, it makes sense: because from the IT perspective, the lady didn't update your name in the other internal system they have. From the human perspective, it doesn't make any sense, because you already told the company about your name change.
I think that it's unacceptable (or at least far away from ideal) when as developers we impose technical complications into how things work in real life.