Everyone in computers has to deal with that. Only difference is the level of expertise it takes to fuck up. As an example, I do QA management for a Bluetooth chip company (we're #1 in the industry, though you've probably never heard of the name). We create this big document that goes out with all of our software releases. It's called "Release Notes." It has the description of the release, the required prerequisites to get it to install, instructions on how to install it, a list of known problems, a list of problems that were fixed in that build and some technical specification data at the end. Guess which parts nobody ever reads? Yep, the instructions on how to install it or the prerequisites. We get calls from customers asking the most basic questions, like "Does the name of your setup.exe comply with 8.3 filename limits?" (The file is right there in the zip for them to see it themselves.) Or my personal favorite, "When we try to install it, we get this error message saying it cannot install because Vista Service Pack 1 and XXXXXXXXXX are missing. What do we have to do to get it to install?"

So, no, it ain't you. The amount of pay you make doing this is largely based on two factors: 1) whether you write anyone else's annual performance reviews, and 2) the technical level of the "Halp, your chit is brok3d, plz fix it" questions. :P Well, and to some small extent, how far up the boss's ass your nose is.