3 ms·
> giving them work is often a form of programming... they will do exactly what you tell them to do Yup. My anecdote: There was a middleware business applicati
by T-hawk 6y ago
> giving them work is often a form of programming... they will do exactly what you tell them to do
Yup. My anecdote: There was a middleware business application. Two database fields were last-changed-timestamp and last-changed-username. The spec document accidentally flipped the definitions, defining the value for last-changed-timestamp = current-username and vice versa. You can guess what got implemented.
"I ran this and got a type conversion error. Did you even test this?"
"Yes that is what should have happened based on the spec."
- PeterisP 6y agoOh, 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.