Model / View

There’s something not quite right about the design. Can we suss it out, or should we make it a bit worse? Lots of musing, very little code. General Wisdom Received wisdom would have us keep “model” and “view” separate. Often the need for this is quite clear. Imagine a bank account, recorded in some database, represented by a raft of transactions, plus a current and pending balance, plus various account information like owners, addresses, tax numbers, and so. That will all be represented, one would hope, in some computer-oriented format. But when we log into the account on its web site, we get displays of that information spread over several pages. When we use the phone app, we get other displays, and when they mail us a statement, there’s yet another display of the same information. So the view essentially translates the computer’s information into something more suitable for human consumption. And the upshot is that there is plenty of design advice out there telling us to carefully…