exposing your internals - visual.ly
I feel sorry for Visual.ly - who have announced what seems like an awesome visualisation service and consequently been swamped by interest. Their website has been up, down and in-between most of the day... I'd love to try the service but have been able to.
The thing that struck me - and it's still pretty much common practice - is the errors spewing out from their pages, for example:
This is bad stuff, because it starts to reveal some of the internal structure of their databases. Personally I feel it is incumbent upon providers of online services, where users create and store data, to be really fixated on security and avoid easily-avoidable vulnerabilities such as this which is a result of lazy developers not turning off errors and sending them to log files instead of the browser. It's fine in a test environment, but not for a production environment.
Not to mention the fact that it looks like some hefty table joins going on there each time the page is hit - no wonder the database feels like having a rest!