You know that an instruction can be short, unambiguous, accompanied by best designed clear easy to understand diagram / logo, and that someone will ignore it and do something terrible.
"A few cans of Pepsi (NOT COCA COLA (http://example.com) and not any diet product please)" does have the advantage of being more check-list like, allowing people to hghlight / crossout the items they've done or not done yet.
The post-mortem of a kickstarter posted to HN yesterday, where someone managed to print and deliver a poster with a misspelling of the word "BROOKLYN" as "BROOKLYIN" has made me think about how people find and prevent errors.
HN isn't a good audience to ask that question because there are different ways to write code. There is only one way to write BROOKLYN.
"A few cans of Pepsi (NOT COCA COLA (http://example.com) and not any diet product please)" does have the advantage of being more check-list like, allowing people to hghlight / crossout the items they've done or not done yet.
The post-mortem of a kickstarter posted to HN yesterday, where someone managed to print and deliver a poster with a misspelling of the word "BROOKLYN" as "BROOKLYIN" has made me think about how people find and prevent errors.
HN isn't a good audience to ask that question because there are different ways to write code. There is only one way to write BROOKLYN.