Although I'm very busy as a SharePoint consultant, I try and answer others questions even if they are developer specific (I'm not a developer). Today's question was...

"Hi Ian, 
We've had a bit of a discussion about logging in xxx - basically what we want is somewhere to log any exceptions, warnings or debug information. 
yyy was keen on logging into a SharePoint List, I was keener to log straight to the Database for better performance.  We don't want to log to the file system as we would then need to aggregate the logs from each of the application servers.
Have you had any thoughts about how we should implement logging?  Are there any constraints that you know of that would prevent us from logging to the database?"

Remember I'm not a developer but 2 things came immediately to mind.

1. Patterns and Practices - Logging Application block
2. SharePoint Unified Logging Service (ULS)

Put the 2 together (using live.com search) and someone else has already thought of the answer (Not invented here :-(
http://www.codeproject.com/KB/sharepoint/SPLogging.aspx

Then add one of the codeplex projects to view the logs http://codeplex.com/Project/ProjectDirectory.aspx?ProjectSearchText=sharepoint%20uls

Talking about quick thinking, one of my passions, apart from SharePoint, is Motor racing. I did take 10 minutes out to watch highlights of the Indy 500 which was just won Buy Scott Dickson, a Kiwi, who dreamed of this when he was just 13 years old. $3.5M well earned. One of my reoccurring dreams is driving an open wheel race car around a track but after watching the Top-Gear episode where Richard Hamond tried to drive a formula-1 car around a race track for 3 laps, I'm under no illusion as to how fast you would have to think and react...