Researcher Carmageddon's event happened!

There was pizza. More pizza would have been better; keeping co-workers who were not attending the event from sniping would have also been better. (I think moving up the delivery time would have helped also, to decrease the window at the risk of possibly late pizza.)

We doubled up on nametags: we had ours that we did, and also the dude who does the meetup had some specific ones. (Ours were pretty awesome, and they worked for the people who just sorta showed up.)

There were a bunch of people who used to work with us showed up: I got to meet the guy who had the cabinets before me. I feel honored.

The libations were no problem as per usual.

My Overlady got where she was going safely (it turns out that a great but one of those things you could never see coming way to stress me out is to have me dealing with a time-sensitive remote travel-related thing in an unfamiliar email system) and stuff. But fortunately it was something where I could just call instead of bashing my head on the email search (I am going to have to read their manual) for the email address that one of the A-Team left us.

I have WORDS for helldesk regarding fucking tags and the fucking trip back from Kipper/Llama. Fuck.

( More things. )

My tweets

• Thu, 14:23: On the topic of the all day offsite: "But the last hour was drinking."
• Thu, 14:30: Here, stick this fish in your ear. #FISHBRICK
• Thu, 14:33: "Incent" is not a verb that I am heretofore aware of.
• Thu, 14:37: It is really awkward being named Azure in this industry. #withachanceofmeatballs
• Thu, 18:00: The party has started.
• Thu, 18:58: Mothfucking lack of tag migration. No one has asked for tags my ass.
• Thu, 19:36: Playing Edward 40 Hands using superglue. #CAH #customCAHcard
• Thu, 20:03: Too many People. Hid in the Renaissance Man's office for a bit.
• Thu, 23:00: Bad crossovers: Karkat meets Odo.
• Fri, 02:23: doublewowee: does anybody else legitimately worry about how they’re going to share a bed with their partner... http://t.co/eAfvuVBPC4

( Read more... )