Dennis cut his coding teeth by teaching himself BASIC on a Texas Instruments TI-99/4A computer in the early 80's. His earliest memory of debugging a program was when he found that his mother had typed the letter O instead of the digit 0 in a hexadecimal string that defined the graphics of a program she copied from the listing in a magazine.
After discovering Delphi 1.0 during college, he went to work on a fax broadcast system and other telephony projects.
In the late 90's he worked with a few record labels to put software on their music CD's. This included Windows screen savers of album art work and a music player that scrolled the lyrics of each song across the screen -- all written in Delphi.
After that, he spent about 5 years doing web development in PHP (even working with a PHP MVC Framework) before discovering ASP.NET and C#.
He remained somewhat proud of the fact that he had never worked with Visual Basic until starting his current job where it is the company's language of choice for developing Microsoft Office customizations for the legal industry. Even though he still gets lost when looking at VB6 code, with the advent of LINQ to XML and XML Literals in VB9, he is happy to be a VB.NET developer.
Dennis was recognized as the 2nd runner up for the Inland Empire .NET User Group (iedotnetug.org) Most Valuable Member award for 2008-2009.
Azure storage for the relational database minded developer
Now that Microsoft has released SQL Azure, which supports nearly all of SQL Server’s functionality in the cloud, why should developers consider using Azure table storage?
Table storage (along with blobs and queues) provide the truly cloud level scalability that you’re looking for when you decide to develop an app for Windows Azure. We’ll start by comparing the pros and cons of choosing Azure Table Storage over SQL Azure. Then move quickly into how to design your data model in a manner that works well with the highly scalable table storage. With SQL Server and other relational databases, normalization was king. However, table storage is not relational and therefore requires a different way of thinking about how to store data.
The benefits are huge, but wrapping your mind around the flat file nature of Azure table storage when normalized relational data models are all you've been thinking about for the last 10+ years can be tough.