> That kind of ontology is useful for writing requirements, use cases, tests, and so on. But that doesn’t mean that it’s useful for writing code the code that implements bank accounts.

Isn't good, easy readable code look very similar to requirements it was written upon?