I have a new tactic when integrating software. First explicitly disable behaviour in your code but write interfaces for it to work.
-
-
Replying to @nouswaves
Then test the interfaces, then implement them. Finally remove the explicit disabled behaviour.
1 reply 0 retweets 0 likes -
Replying to @nouswaves
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.
1 reply 0 retweets 0 likes -
Replying to @nouswaves
A living document of behaviours you don't trust. if (someUnexpectedButPotentialllyAcceptableInput) { throw Error("Not yet."); }
1 reply 0 retweets 1 like
Whitelists make exceptions implicit; blacklists make exceptions explicit. Of course you want both, but you don't just want a whitelist.
10:05 AM - 23 Jan 2014
0 replies
0 retweets
1 like
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.