I have a new tactic when integrating software. First explicitly disable behaviour in your code but write interfaces for it to work.
Problem this solves is that sometimes what you're integrating with is very open with what it accepts but you haven't tested this behaviour.
-
-
A living document of behaviours you don't trust. if (someUnexpectedButPotentialllyAcceptableInput) { throw Error("Not yet."); }
-
Whitelists make exceptions implicit; blacklists make exceptions explicit. Of course you want both, but you don't just want a whitelist.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.