Why should I spend time troubleshooting a problem with code for my website?

Its tedious, its pedantic, and its not my biggest bogey right now.

I should be able to put my website on a server, call technical support, and have them explain to me what the problem is (if there is one).

Thats the stance I took when I started looking for someone to host my website. I didn't want to spend my time worrying about whether the site was up or down, or whether my orders were being processed correctly. I also didn't (don't) have time to spend all day designing and writing webpages that may or may not work on some web hosting companies' webservers.

The truth is, I had a girl write my website and I think she just left for college... and the guys I found to do it on the internet charge me per hour. What I need for a great website is excellent customer support and servers that work with my website design. I need to write a website once, upload it to a host provider's server, and have the site up and running 99.999% of the time. Is that too much to ask?

Well, I went out there asking ALOT of providers for what they thought before I started spending any more money. The truth is, most providers follow the addage "the customer is always right". This conventional wisdom seems to be forgotten with certain web service hosting providers who have opted for quantity of subscribers over quality of service.

The most frustrating conversation is one where I explain my problem to a customer service person, and they say "well, its sounds like a problem on YOUR end". I'd like to explain to the person who gives me that answer that "I don't HAVE an 'END'. The END is YOUR server!"

Fortunately, I actually found some providers out there who are large enough to have all the resources available to answer the questions I had about ALL of the technologies I used to build my website (mostly HTML and PHP), as well as questions about where I would like my website to go and the services that were best for my planned growth.