David BissetDeveloper: "We don't need to write documentation. Users should obviously know what to give as input. "
Users:
Deb has moved! (see profile) 🇨🇦@davidbisset 🤔 reminds me:
There's a version of that called poka yoke in Japanese.
https://en.m.wikipedia.org/wiki/Poka-yoke
Colloquially:
mistake-proofing or idiot-proofing.
Ex: it's impossible to put a car's automatic transmission into Reverse while the car is moving forward.
For a poka yoke designed CD player, *only* a CD would be allowed to enter.
All other schemes require instructions!
(Or, sell it so cheaply that we can throw it away when it breaks: dollar store junk)
@deborahh wow, that's interesting... and smart.
@davidbisset only as smart as your code, though. Isn't that what you want to test? 🤔
Seems kind of like Dunning-Kruger, but for tests. I don't see evidence, in the anectodal reports I've read, of chatGPT know it's own limitations. Quite the contrary, at times ;->
/cc @GeePawHill @jbrains
J. B. Rainsberger (he)@deborahh @davidbisset @GeePawHill One of the most elementary forms of poka yoke in code regards designing statements that must follow another, such as "A must happen before B".
To enforce this constraint, let A produce a result that becomes an input to B. This way, there becomes an obvious way to compose the functions that preserves the required sequence.
Let's do more of that kind of thing.