I still remember my days as a developer, I never took care of Error 404, Error 500, etc till the very end, when the UAT came back saying the application is broken. A mere small setting took care of those.
I realize now the importance of informing users, when my blog and my photo stream crashed because of errors and broken link.
Well, its never a great experience to have that page in front of you, users either click the home page back and to a search or just close the browser. Like I do most of the times on MSDN. I just closed the browser and went back to Google to search some other resource.
So what do I do, I go and explore a few websites and I found this very interesting website which lists out Error 404 designs. Now that's creative, and I definitely am not losing my patience when I see one of those.
Pattern Tap is one great website or say a repository. Check the Categories and I am sure you would feel overwhelmed as I did.
My personal Favorite
