A wife tells her programmer husband: “Go to the store and buy a gallon of milk. If they have eggs, get six.”
He comes back with six gallons of milk. When she asks why, he replies: “They had eggs".
A wife tells her programmer husband: “Go to the store and buy a gallon of milk. If they have eggs, get six.”
He comes back with six gallons of milk. When she asks why, he replies: “They had eggs".
I’ve never liked this joke. I guess it’s supposed to be that the husband does the literal action as described, but instead it’s just that they interpreted ambiguity opposite than expected? It just really doesn’t work very well :/
Given the stereotypical difficulty of “product folks” and programmers agreeing on and building shared understanding of what to build, this joke seems clear and straightforward. It works because of course, the customer and the programmer failed to agree on something simple.
That is why we have spec docs, duh. /s
Maybe it’s just worse when written. The period at the end of the sentence makes it hard to see how it could be misunderstood.
To your point though, not sure if I’m aware of any programming language that would continue a statement with a following if block. Far more likely that it would fail due to lack of an element to apply the 6 to rather than having a pointer to the previous object, or he would try getting what ever the literal version of a 6 would be, or maybe some slang version.
any language that allows ternary conditionals
Those would all start with the if, followed by two conditions, not a statement and then an if. There would be a condition to evaluate, followed by then/else?