Back up any personal (NOTE: NOT CORPORATE IP!) data on my work laptop whenever I get a context-less "let's talk" message.
Putting all of my corporate expenses on my personal card, then expensing them instead of the other way around to avoid giving them the "well technically this might be embezzlement" stick if they disagree with a decision.
Never having more personal items at the office than can fit in my backpack in case I get fired.
Emailing after a verbal conversation to record the next steps agreed upon so I couldn't be gaslit later.
Not updating LinkedIn until I'd been at the company for the better part of a year.
Not trusting the positive feedback bracketing the negative feedback in the middle of the Shit Sandwich because I know later it'll turn out that was their version of putting me on a PIP.
Treating employee surveys that claim to be "anonymous" the same way I treat emails from companies telling me that my privacy is "important" to them.
Making a pact with a peer in the first few months of a job to be each other's "supervisory reference" when interviewing elsewhere.
Having a @textexpander fill-in-the-blank resignation letter ready to go at all times. I'm not kidding; here:
Assume corporate computers are rooted, keylogged, MitM'd, and have the cameras + microphones enabled at all times.
Only ever giving my employer my Google Voice number, not my actual cell number.
Never, ever, ever, ever install MDM on a personal device. The only way they should be able to wipe data is with a hammer.
Go into meetings expecting the absolute worst case disaster scenario just to avoid being disappointed by the outcome.
Carefully look at how former employees are spoken about after they've left, and leave clearly documented decision documents scattered throughout the environment to avoid being slandered later.
Have a mental dollar figure for how much money you're willing to have stolen from you. Don't ever charge a dime more than that amount at one time to your personal credit card for the company in case they don't approve the expenses.
Maxing out my PTO accrual so they're forced to pay me out at least that much when I get Surprise Fired down the road.
Discount any GlassDoor reviews that don't list actual serious drawbacks, because they probably have internal "write about how great it is to work here" workshopping sessions.
After enough of these I kinda snapped. When @mike_julian and I started this place we swore none of this kind of crap would be necessary.
We strive mightily to ensure that it never becomes so.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
It wants an S3 bucket. Cool. The service has one bucket for ingest, and one for output generally. Which does this form want?
ALWAYS WITH THE QUESTIONS, YOU PEOPLE!
"Encryption of S3 buckets is basically a box check for compliance groups. That said, we at @awscloud are going to mandate it for this service with your own KMS key because the KMS team bribed us for that sweet $1 a month revenue juicer."
So back in 2008-ish, I volunteered as freenode network staff, which I was for the next seven years. This still occasionally surprises people. My nick was, unsurprisingly, "Corey."
I'd been on the network learning for a while, primarily in the postfix and centos channels. (That's how I met @BitIntegrity, whom I later married. To someone else.)
It was nice to have a chance to give back.
There was a lot of fun, a lot of drama... @bequinning and I flew out for annual holiday gatherings in the UK for a number of years.
Eventually I stopped having time to spend on IRC, and focused on other things. Like shitposting here!
In this "welcome back to @awscloud" thread, I'll take new AWS CEO @aselipsky through a whirlwind tour of what AWS has been up to during his time away.
I know his first day was Monday, but the CloudFormation thing that was going to tell me when he got to the lobby was wedged in ROLLBACK_FAILED, so hopefully he was able to at least find the bathroom okay...
As I'm sure @aselipsky remembers, @awscloud prides itself on being misunderstood for long periods of time. It'll sometimes be first to market with something they refine, or late to market with something polished. Their Kubernetes option went for novelty: both late and underdone.