A response to your comment
I'm not getting into the debate of who has it worse - programmers or admins (because I've actually done both jobs and know that each has its own pressures) but I'd like to respond to some of your constructive arguments:
"In my (actual) experience, when developing in ANY way, shape or form, you are not working on a LIVE system. This means that it is a system that is not in use during standard business hours."
Except for when a system is not tested and pushed out to live, then the customer complains that it's causing business critical issues because they wanted it in live yesterday regardless of whether they'd tested it properly.
There is such a thing as DR - if a live system fails, the DR environment should be able to take over if necessary. You can't correct a malfunctioning bit of functionality so easily.
"We can't pass the blame like programmers do either"
Believe me, I've seen so many more cases of sys admins passing the blame. "The server's up, but I can't investigate it any more than checking I can log in because I don't know what the application's supposed to be doing."
"Although I stilll believe admins have it far worse, I understand developers, in cases, have to deal with the same."
I have to disagree. In all the businesses I've worked with, the first point-of-contact for a frustrated client whose system isn't working is the developer. "The developer made it so they should know what's wrong." Most of the admins I've known only ever had to deal with the developers or the support desk.