The reason this blog exists

My Treo 650 is malfunctioning. The speaker is dead, the phone doesn't ring and I can not use the speaker for hands free conversation.

I call my cellphone provider, the lady puts me on hold for over 20 minutes. She explained to me at the end of the 20 minute wait period that she can not order a replacement for me because my phone belongs to the company I work for. To get a new phone, I need to call our Point Of Contact person and have them order a replacement unit. I asked the lady what she was doing for 20 minutes while I was listening to soft jazz. She said, she was trying to lookup contact information for the "Point Of Contact" in the system.

This set off alarm bells in my mind, does it take 20 minutes to look up a phone number? What kind of app is that? How terrible does the code need to be for a 20 minute phone lookup?. Yahoo can search thru billions of records in a split second, but my cellphone provider takes 20 mins to lookup a record in 20,000 records ?

The reason this exists today is typical IT exec does not care about improving the application performance. They simply don't have an MBO that requires them to improve the performance of the application. The CIO's don't pay enough attention to application response times, they care about bigger issues such as buying $20 million worth of new hardware. An average DBA is just happy that his database isn't crashing - he barely has time to deploy new applications - he simply can not afford to tune the database. It isn't a priority.

What is the end result? The end result is me waiting for 20 minutes on the other end of the phone.

So, to contribute my 2 cents to the ever increasing information clutter in blogosphere, I will start blogging whenever I see a blatant slow performing IT application.