After Toms intro, I can't stay behind. I've been working in IT for about 10 years now, mainly working as a consultant for various shops, both large and small. Other random facts: I have a degree in Astronomy, a Norwegian forest cat, 2 daughters, I live somewhere between National Park "Utrechtse Heuvelrug" and de Veluwe and sometimes strike people as hyperactive (which I'm not).
My professional background started with developing line-of-business apps with MS Access. In that first year of my career I learned a lot about what problems businesses and business users run into, and the great part of using MS Access was that most projects had limited scope but surprising functional coverage: data modelling and entry, reporting, ETL, etc.
It also planted a seed for the urge to constantly improve as many things as possible about the "developer experience", for lack of a better term. By this I mean everything that influences the quality of code written and the efficiency of writing it: tools, guidelines, frameworks, even the keyboards in use
After this flirting with arguably one of the best RAD tools out there (yes, still talking about MS Access), I got involved on the Microsoft web stack, meaning classic ASP, VB 5/6, COM+, Windows DNA, that whole can of worms. Again, working with these tools, I always tried to come up with ways to reduce the pain and strain of developing software (and we had a lot of that in those days). This was also the time I realized that no, I wasn't that elusive consultant that can do everything perfectly: sure, I can design a user interface, but I'm no user experience expert. Fine, I know something about firewalls, protocols and tunneling, but I'm by no means an infrastructure guy. To cut a long story short: I learned to focus, to concentrate on specific skills to get ahead. I dabbled a bit in DBA roles, but at the heart I am a software developer with a slight tendency for web technologies.
Luckily for all of us, the world moved on since Windows DNA, and .NET has been upon us for quite some time. To accompany this framework, Microsoft has rolled out an impressive stack of server products to support all sorts of scenario's: stuff like BizTalk, SharePoint and SQL Server with all its BI bells and whistles to name a few. These days I often work as a solution architect, which means I have to know a bit about most of these products, but again, they are mostly outside my focus zone. I continue to focus on the developer experience, trying to share both knowledge and enthusiasm along the way. Design patterns, principles like SOLID and DRY are high on my list of intended topics, but I also expect some less-focused (but equally interesting) ramblings on things I run across.