NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
What brought this about and the reply (Score:1)
A recruiter mailed me -- unlike the last 1,000 recruiter emails, it was intelligently written and persuasive. It earned a reply. But which reply... I don't want to just say "no". Any reasonable offer will be considered. But I don't want to flop back to full-time work again as my consulting is starting to stabilize again. Last time was a disaster. But I'm really not making a living wage now...
Anyway, for posterity, here's what I have as a reply... I'll probably tone it down a bit before I send it, but
Re: (Score:1)
And now the reply looks like this:
------------------------
It's true. I'm spoiled rotten as a consultant. A company would have to make
me quite an offer to lure me away from this. But I'm open to offers. I'm not
interested in more money than I have time to use. What good is a fat salary
if you can't ski on it?
Working in a company, there's no prospect of getting your work done and then
taking the rest of the day or week off. The primary incentive is missing --
finishing. You have no veto over ill-concieved
Re: (Score:1)
I call this process (of 40 hour typing sessions) "bugging", since the inevitable result is 10 hours to "bug" something and 100 hours to debug it.
"Bugs are inevitable. All software sucks."
Sure, when you have a bugger writing your software instead of
Re:What brought this about and the reply (Score:1)
Reginald Braithwaite had a great post about this the other day: Bricks [raganwald.com].
Reply to This
Parent