That is the truth. I had a friend that I built a computer for, and it was actually a pretty painless experience and she never really bothered me with questions.
Fast forward a few years, and this friend mentions that she wants a web site. I know where this is going so I kind of ignore the request. Fast forward a year or two later, and she contacts me and says "Hey I signed up for this web provider but I'm confused on how to make a site and if you help me, I'll make you a free dinner." I HATE building web sites -- I like architecting the underlying infrastructure, but I hate making content and keeping it current.
Anyway, I generally ignored her or told her things like "Just get on your provider's site, as they have to have instructions." After more nagging, I finally said "OK, give me the name of the provider, the address, and the credentials and I will take a look." I logged in and they had documents with STEP BY STEP, ILLUSTRATED INSTRUCTIONS with ACTUAL SCREENSHOTS on how to connect and build a site with stuff like Frontpage (which she had). I downloaded the document, attached it to an email, and said "Here, follow these and you will have no trouble."
I got an email from her a couple months later. "I'm confused about these instructions and need your help." I deleted the email and ignored the request. Seriously, a 12 year-old kid could build a site with those instructions. It wasn't that she was dumb; she was just too lazy to read the damn thing and just wanted me to do it for her. That is the type of person I don't like to help -- the ones who make zero effort at finding a solution or reading documentation.
For that matter, I was also the same way with help desk associates. If they came to me with questions on how to fix something and couldn't outline the troubleshooting steps they had taken that yielded no results, I would tell them to pull up Google and not to bother me until they had thoroughly exhausted all possible solutions and I expected a list of actions they tried.