M Paquette
Moderator Emeritus
How I did it? Good question.
Since I was on good terms with the whole management tree, and was in a sort of important individual contributor (non-management position, I quietly verbally informed the managers about 4 months prior to departure. That way they were able to bring in someone, who was co-located in the office I used when I wasn't telecommuting. We worked together on an orderly transition, with him initially shadowing me, then about a month before departure, I shadowed him as he took on effectively all the work.
This probably sounds a bit weird compared to some of the workplaces out there, but this was a fairly large business, chock full of engineers who tended to be pretty orderly and 'grown up' about this stuff.
About a month before departure my boss did mention that I should probably find some way to quietly let others know that I wouldn't be around. Good point. A bulk "OMG! I'm out of here in a month!" e-mail would work, but that's a bit rough to send to 12,000 co-workers. So...
I decided on a more subtle approach. I blocked out my schedule in the company wide calendar app from the departure date to 2032 (as far as I could). That made sure that I wouldn't get meeting invites or be scheduled for presentations without my knowledge. Since I didn't want anyone to be shocked when mail to my company address started bouncing, I tucked this into my work e-mail signature:
One week prior to departure I started schlepping company assets from my home office back into work.
About 3-4 days before departure I started not taking things all that seriously. An e-mail from that period:
Since I was on good terms with the whole management tree, and was in a sort of important individual contributor (non-management position, I quietly verbally informed the managers about 4 months prior to departure. That way they were able to bring in someone, who was co-located in the office I used when I wasn't telecommuting. We worked together on an orderly transition, with him initially shadowing me, then about a month before departure, I shadowed him as he took on effectively all the work.
This probably sounds a bit weird compared to some of the workplaces out there, but this was a fairly large business, chock full of engineers who tended to be pretty orderly and 'grown up' about this stuff.
About a month before departure my boss did mention that I should probably find some way to quietly let others know that I wouldn't be around. Good point. A bulk "OMG! I'm out of here in a month!" e-mail would work, but that's a bit rough to send to 12,000 co-workers. So...
I decided on a more subtle approach. I blocked out my schedule in the company wide calendar app from the departure date to 2032 (as far as I could). That made sure that I wouldn't get meeting invites or be scheduled for presentations without my knowledge. Since I didn't want anyone to be shocked when mail to my company address started bouncing, I tucked this into my work e-mail signature:
Two weeks prior to departure I provided my boss with an official resignation to forward to The Forgotten Old Ones that ran HR.Mike Paquette
mpaque@BigFruityCorp.com Warning: E-mail address expires March 7, 2008
One week prior to departure I started schlepping company assets from my home office back into work.
About 3-4 days before departure I started not taking things all that seriously. An e-mail from that period:
From: Mike Paquette <mpaque@BigFruityCorp.com>
Subject: Re: CGContextFillRect
Date: March 3, 2008 3:24:12 PM PST
To: Red Acted <redacted@BigFruityCorp.com>
Correct. There's no hidden back-channel between the CGContext and CGColorCreate() to propagate any information on the colorspace to be used in creating the color.
For example, the use of a cat-based colorspace has to be encoded with the color, so that when a CGContext sees that CGColor, it will know how to interpret and translate the color into the destination colorspace.
Subject: Re: CGContextFillRect
Date: March 3, 2008 3:24:12 PM PST
To: Red Acted <redacted@BigFruityCorp.com>
Correct. There's no hidden back-channel between the CGContext and CGColorCreate() to propagate any information on the colorspace to be used in creating the color.
For example, the use of a cat-based colorspace has to be encoded with the color, so that when a CGContext sees that CGColor, it will know how to interpret and translate the color into the destination colorspace.
Last edited: