Why don't tech writers get a life?

Two years and a half ago I decided I could be a technical writer. In the meantime, I realized that being a technical writer sucks. Mind your cons on this one, as a list of highly well-grounded reasons follows:

1. At the interview: Though everyone in the company is a skilled documentation writer, as you are told, they don't have time to handle the documentation anymore ... Therefore, they are hiring a tech writer. On a second thought, they'll hire two tech writers.

2. First day at work: You are really needed in the organization, they say, but for the time being there's no documentation that needs to be written. Try to look busy and you'll be alright.

3. First month: 'Still no work for you huh?'

4. Second month: 'Don't worry, we'll find something that you could do around here. Eventually...'

5. Shortly after: 'We finally have something for you. Do you think you could write the help manual for this application by next week?'

6. The next day: Someone has to train you a bit in the new application, you're told, explain you a few things... But nobody has time today. Ask again tomorrow.

7. 'Ask again tomorrow.'

8. 'Today we're all in a meeting, 9 to 5. We'll talk next week.'

9. Finally, somebody remembers you:
'How's the help manual going?'
'I was just about to ask if anyone has time for that discussion today...'
'This week it would be pretty much impossible.'
'But I thought it is due next week...'

10. In one year or so: 'Think you could learn MySQL?' (In the end it is revealed to you that you can't help with MySQL either. There's plenty of trained staff in this field already).

11. In two years or so: 'We might need to let you go after all... No hard feelings, OK?'