Account inactive @literorrery@awoo.space

I just came home from an amazing group date with the polycule. I got to spend the whole day cooking -- sausage patties, cornbread stuffing, creamed corn, mushroom gravy, chocolate mini-tortes, and chocolate orange creme patissiere -- and then we went to see Black Panther together. I had an amazing time and I hope we get to do more stuff like that!

I will listen to those who want to explore their feelings. I will reify and validate their emotions. I will acknowledge their pain. I will sit in the fire with those who suffer to help them not feel alone.

Ask me to step into the flames and then attack someone else, and I'll call down the fucking heavens. I have little enough patience for people who can't draw a line between "I hurt" and "they hurt me." Less for those who can't separate "they hurt me" from "they're categorically bullies."

The long-term solution is to make the remote system do the lookup in the legacy system and fetch the internal GUID for us, but that could take three weeks and I can get this hack done today. And the real long-term goal is to get off the legacy system with its internal GUIDs, but we can't afford to do that if we can't make these legacy calls in the meantime to let us not have to reinvent the entire system from scratch before we use it.

So right now, I'm working with one of my coworkers to create an encoding scheme so we can encode the data we need, which contains spaces into a data tag we can append to the data we're already getting through a system which strips spaces, so that we can unmunge the data ourselves on the receiving end to get back the string we need to do the lookup to get the data we actually need so we can execute the function we have to call without having to rely on the legacy system's internal GUIDs.

I'm unconscionably angry right now, because I was so hung up on whether or not I'd be able to interface with the old legacy system that I never stopped to ask whether the new system would be feeding me the data I needed to make the old system do stuff. And it _can_, but it presently... isn't.

... and today we've discovered that the input field on which I've been relying to link data between two systems is, in fact, not shared between those systems. It _can_ be, but there's no mandate that it must, so our hit rate is low teens. Because everything is a manual process and nobody has a consistent data model and my project relies on interoperability between those systems.

Smutty RP through LinkedIn messages is the new sex on the boardroom table.

I just made what amounts to chocolate orange foccacia with orange water icing.

It's weird and good and weird. But good.

Also, that jar of yeast is dead.

Transition Goals:
* Eye color outside CIE1931
* Tarnish-proof exterior
* Main gearing adjusted to seven
* Engraved ritual bound
* At least two modular artifact slots
* Noise-dampening outer shell
* Onboard reality-distortion field
* Thigh gap

I flew too close to the sun. Sunday's leftover beans seemed like a small step up from yesterday's pea soup.

It was a major leap. Off a cliff. Into the sharpened rocks at the base of the waterfall.

I'm not healthy yet. I just don't feel ill.

I spent three hours on a work call on a sick day. How you?

And to his absolute credit, when I told him "I have the flu; I'm not going to put a date on my wellness," he offered to send a tech to the house instead of demanding I drive somewhere to drop off the old modem. So, props to you, "Paul from Atlanta."