In the past, I was a Microsoft guy. Going all the way back to 1983 when I was working for a small company in Nashville where we hooked a Corona PC with DOS 1.0 to a Ricoh laser printer through a Black Box for desktop publishing. DOS 1.0 was my slave. I knew every command and every switch to make it do exactly what I wanted.

I built EDI systems on a room full of 386 machines, 1200 baud modems, and Microsoft Windows 3.11. The MS FoxPro apps we created turned into separated tiers of architecture with SQL Server, C++, and NT servers.

SharePoint became the fastest adoption product ever released by Microsoft. We helped big corporations install, configure, implement, and manage the 12 month projects for MOSS '07. Dang, everything MS became so complex that a huge industry flourished around consulting just to use the tools.

Now that I'm into load testing, I sit back and wonder what would have happened if I stayed in the MS world. Thankfully, I am MS free now. Averaging 3 blue screens per day on my Dell laptop became too much and now I love my Mac and iPhone.

What's that got to do with load testing? I found a link to a blog post about MS load testing. I went there to check it out, with genuine desire to learn something, but was quickly befuddled. Even the blogs about using MS tools have gotten complex and confusing. How can anyone live in that environment?

Take a look for yourself. Ed Glas's blog on VSTS load testing

Notorious MS bugs too. Lions and Tigers and Bears...oh my!

I am so happy that we have found a simpler, easier, kinder, gentler way to do load testing.