If you don't share my opinion that CSV should be banned by an international convention, it might be because you've never had to write code to read a CSV file.
I've spent the last couple of weeks hanging out on StackOverflow, and thinking about how successful its design is.
Just a quick one about a SQL 2005 message that I found; I've also found quite a few unanswered questions about it on other forums so thought it might be worth posting here.
If you buy a new PC or laptop these days, it likely to come with all kinds of unwanted junk: trail versions of antivirus, browser toolbars, CD-burners that replicate that the OS can already do by itself, and so on. There's a great little utility called The PC Decrapifier that can help clean this up. Its basically a script that searches the PC for 'crapplications' and then gives you a list of what it finds. You then choose the ones you want to get rid of, and it gets on with it for you.
Recently I was updating some ASP.NET pages for a client. They had a set of custom-built server controls that worked very happily, binding data to and from domain objects. I modified some of the ASP.NET pages so that they became Content pages that shared a common Master page. Then suddenly all the Server controls stopped working - they were not processing postbacks properly or firing events. That is, Server Controls that had worked in normal ASP.NET pages suddenly stopped working in Master-Content pages.