I want to ensure the app is pretty robust.
By which I mean that it shouldn’t crash (much).
This obviously involves writing proper code.
It also involves dealing with user input and the Flickr API in a sensible manner.
It’s reasonable to state that no user input should cause the app to crash.
To achieve this aim I will be treating all user input with extreme prejudice.
By user input I don’t just mean forms on the site.
I also mean any form of “URL hacking” too.
I also need to look at all the possible error conditions that the Flickr API can throw at me and deal with them gracefully.
Errors from Flickr will either be network errors (come back later when it’s better), invalid XML (will need to be investigated to see if I can work around it) or one of its published error codes (should be the easiest to deal with).
* Robustify is a word some shit contractor used in a CVS commit message after I slagged off his toString method.
I think it’s an awful word so therefore I enjoy using it in an ironic manner.
And now, for some gratuitous photos.