Working with bad hosting providers.
I can break it down to three main problems I have with "bad" hosting:
1 Working with no shell access
a) I've lost files when moving them between two folders:
how in the world does cpanel manage to mess up
mv /* ../?
2 Working with no control over resources
a) I've wondered for a couple of hours why a migrated website wasn't working properly:
Hard drive was full. Cpanel didn't complain (Actually, instead of scrolling down to the
last performed copy, it displays the top row of the log by default, which is so useful
compared to shell commands).
b) Having to call customer support to increase the PHP memory limit.
Thanks guys for the default 64MB. You know, you could have displayed the memory limit somewere in the UI, like, right under the bandwidth and hard drive usage?
c) You cannot optimize without basic access to configuration files
Some shared hosting providers get it right. Some just don't. And you have to live with that.
3 Working without automation
If you're stuck working with #1 or #2, tough luck, you can't fully automate tasks.
Don't get me started on what could be automated with shell access. I could do migrations, cloning of websites, automatic optimization, automatic backups and deployment with a single click.
Any cost they might think they are saving by hiring a cheap hosting provider is offset by the extra hours they have to pay me to work with their broken tools.
Bottom line: Next time I'm looking for a job, I've got to do a lookup on who is hosting their company website. Chances are, they use the same hosting for their clients.
I should probably automate that and turn it into a website... :)