Oh, I've got a relevant story. There was a spec sent overseas for a system where one of the entity descriptions had a typo - in the title instead of 'Customers'

Oh, I've got a relevant story. There was a spec sent overseas for a system where one of the entity descriptions had a typo - in the title instead of 'Customers' it said 'Custoners'. The 'Customers' table was referenced in multiple other places and tests, so the delivered system had no problems with that, the customer functionality worked properly; however, sure enough, in addition to the 'Customers' table the database schema also had a table 'Custoners' with all the fields. Because the specification required that.