Awesome. We had twins a couple weeks before you had your singlet. There are some great 'support groups' in the bay area. :) MPPOM is cool. My wife really enjoys it, and the people in it: http://www.mppom.org/. They have expectant parents meetings too. Let me know if you ever want to chat about it or ask questions of a fellow geek and parent of multiples.

We send hundreds of thousands to millions of emails per day, depending on the day. You left out one important/annoying bit. You also have to contact all the major email providers ONE BY ONE to make your emails get through. Microsoft, Yahoo!, and AOL all had specific methods of getting massive amounts of e-mailing to work. Luckily they all included links in the error messages, if you read your SMTP logs. Then you have to make sure your include all the CAN SPAM stuff (send from an address that can be replied to, double opt-in, include an unsubscribe link, etc) and also constantly monitor the common black lists. After all that, you have a decent chance of getting your emails through... It sucks.

Nice one Jeff. Sorry to lead you astray. If you notice near the middle of my article I did mention that the reason this even was an issue was because I was doing orders of magnitude more queries than I should have been. I just found the whole situation quite interesting, in that the query compile overhead took more time than the SQL database query (the DB was running locally with the web server). For that low usage application it wasn't worth the time to do the macro optimization and the micro was fine. Sometimes crafting a better algorithm isn't worth the time. :) I now use Linq to SQL very heavily in online games with millions of users, partitioned databases, and tens of thousands of simultaneous requests. Very few queries are compiled due to well thought out algorithms. Now our biggest CPU bottleneck is Linq to SQL's dynamic update system that uses reflection, so we use SPROCs for critical areas. But, all-in-all, the ROI in Linq to SQL is great.