There is, I think, an inverse relationship between how many meetings you have for a project and how organized the project is. I have one ongoing project which meets once every few months. It's on track and great.
I have another one which misses deadlines regularly and frequently gets midway through a dev cycle to realize they need to change their entire approach. Six planned meetings this week, and usually has 2-4 more with short notice.
Currently starting the second hour of a 30 minute meeting.
Honestly the thing I hate most about working with this dev team. They don't overrun by a few minutes, they overrun by half an hour or more.
And, vexingly, CANNOT answer questions, they'll just point me to these 50-90 minute recordings and say "Listen to the meeting, we discussed it." Yeah, I want to waste an hour listening to developers chatter when you could just say "We added one endpoint, it's ___."
Huh. My github branch for these edits is pull #69. Nice.
So... are there any new cars which can be disconnected entirely from the Internet?
(Spouse and I are looking at new vehicles, preferably EV. Spouse is Deeply Uncomfortable with how the cars we've looked at all have built-in GPS and remote access options so someone can disable the car remotely. It seems like a good feature for the owner, but a bad actor could also use it of course.)
Was just at a public restroom which had a baby changing station. I misread the sign as "baby charging station". I gues the "C" in USB-C stands for "child".
I can acquire a home freeze dryer for about $2000. This is like when I found out I could just BUY a nitrogen condenser, or a still.
These are powers I should not have. Fortunately I *currently* possess sufficient self-control.
(My self-control is currently upstairs sleeping, but they are nonetheless effective. "Why did you spend $4000 on lab equipment?" is not a question I want to be answering.)
Mgmt: Have you documented this user story?
Me: Hm, they say it's done but don't actually say what they did. I'll ask Dev.
Me: Dev, can you tell me what you did to resolve $story?
Dev: I resolved it.
Me: By doing what?
Dev: ????
Me: Just tell me the API endpoint you added.
Dev: ????????? I don't understand.
Me: You said *in your notes* that you added an endpoint for this. What is the endpoint?
Dev: ????? I do not understand your question.
I cannot fix this. It's a damned brick wall.
I am always frustrated by shipping services like stamps.com. I get a notice that I'm receiving a package from, like, Davenport, IA. I have no idea what I ordered from Davenport, IA. And it's a notice the shipping label was printed, so I will receive the package sometime between next Wednesday and the heat death of the universe.
Could developers PLEASE learn what "overloaded terms" are and STOP USING THEM???!!!!
I am currently documenting "objects", "skills", and "tools". There are, in fact for a very specific and quite niche thing, but good fucking luck figuring that out because everything has the most bland-unsearchable name possible.
The "common objects" are even going in the "objects" folder. Thanks guys. It's all a kitchen junk drawer now.
Shoutout to my spouse, who accepts that I will on occasion inflict experimental cookery on them.
(Current plan is that I do something reliable with lots of leftovers on Monday, then something experimental on Tuesday, so that if the experiment sucks we have a backup plan.)
