They don’t have to “notice” it. They don’t even have to see it.

Do you have an access badge to get into your company campus/building/suite?

My last job started tracking access badge activity to monitor and enforce RTTO compliance.

Found it funny to get nagged about not hitting the required minimum number by a boss who lived four states away.

Laughed all the way out the door and into a new company whose policy is “if you wanna wfh, then wfh. If you want to come to the office, be our guest.”

Happy to have discussions and elucidate to others the change, and make whatever documentation necessary available, but if some leader somewhere things I’m a “problem” for merely having done the work…okay, let me solve that problem too: bye.

That’s an environment with serious trust issues manifesting as micro-management and I’ve got a severe case of post-micromanagement-stress-syndrome.

Asking as someone who otherwise generally agrees that there are some truly poorly written errors and exceptions out there, but has also been on the admittedly frustrating end of the constant requests for help deciphering error messages that were very plainly stating what the problem is for someone who didn’t even try looking for the fishing rod.

For someone who was born speaking English and spoke it their entire lives, the example provided couldn’t possibly be more to the point in my opinion.

Though I agree overall with the general idea and that yes there are some pretty baffling and downright awfully written error messages and log entries that take a minute to grok (I just don’t think the example replied to is one of them).

Can you help me understand what isn’t clear about the message as is, or maybe point out the ambiguity to someone who just isn’t seeing it? I want to write better error messages but I share the frustration of the above poster. The message tells you specifically what to do, but you’re coming back saying it’s not clear.

I’ve sent birthday gifts in the mail, and I’ve gotten gifts in mail from these very people.

Sometimes, when I wonder where the convenience that gets talked about in the context of Facebook and “staying in touch” ends and a more delicate form of “you’re probably not as close to some of the people on your friends list as you think” (which was absolutely the case for me) begins.

It took really minimal effort on my part to find other ways of staying in touch, but I think maybe the key is you have to WANT to stay in touch with people?

Just a shower thought.

Sorry for my french but

Jesus fucking christ, thank you.

I was being woken up constantly at last job due to a bug in the application because I was the Devops guy and this is exactly how I was treated. I spent weeks finding contributing causes to frequent failures. Gathered all the evidence I could find and begged for a fix, I scheduled calls with the product team; I poured over documentation and diagrams “this is the problem, this is inherent to the way these requests are being made, until it’s fixed we have no choice but to throttle the app”. I recorded a ticket each time I got paged and linked back to the team who owned the feature.

What was infuriating in the end was finally being told that they knew about the problem long before I brought it up and even HOW to fix it; it was just consistently being deprioritized by people who had the means to influence the decision on “fix this” or “write new shit”. Eventually I just suppressed the application in PagerDuty and stopped waking up whenever it would fail.

SLA slipped, customers complained, I find myself in a meeting being asked very aggressively “what’s being done about this and why are you ignoring PagerDuty?”

I said I wasn’t ignoring PagerDuty and presented a log of 20 something tickets I created linking back to the original “Please fix this request”. I told my leadership “I’m not the one ignoring this problem, I have been trying to get this addressed and prioritized for months”.

Laid off a month later. It’s becoming a growing reason why I want out of Ops and never want to return to it: companies hiring Ops people and treating us like the kitchen sink for work the company is too lazy to actually address and properly prioritize through staffing, planning or both.

It started as an MMO? I never knew this and have got to go read about it now, that IS an interesting pivot.

…what? Is there a laugh being had that’s going over my head? I’m still kinda waking up

From the rest of your comments you seem pretty confident and specific about not having these problems, so I’m curious to know what’s in your secret sauce.

(Interestingly once I scared off a potential dating partner who is heavily into texting constantly and called me out for my asynchronous messaging habits and I flatly responded “sometimes I just want to put my phone down and do literally anything else”)

I love my friends. I hate how they communicate over text.

Back in my teens I was really wanting to get into 3D animation and virtualdub was one of the first tools I used to create reels since the free modeling and rigging tool I used at the time didn’t have any editing capabilities.

I wouldn't necessarily agree, but curious to hear this thought developed some more, if you'd be willing to indulge me? Maybe I'm missing some implied context here that you have experience with that could change my mind.

where does the opposite idea stem from?

Good question. For me personally, it stems from my subscription to the dichotomy of accidental vs. essential complexity as written about here (and other places) https://simplicable.com/new/accidental-complexity-vs-essenti...

Sometimes complexity is unavoidable, but I don't conflate something being complex with a thing being complicated. Complicated systems I would agree, are inherently problematic.

(also, your username just made me very hungry for a falafel sandwich. Excuse me for a moment)

That’s fair, that’s valid, that doesn’t however strike me as a compelling case to go off and hoist all of your stuff into k8s if there’s other equally performant and fault tolerant methods of running your application that require less operational complexity and cognitive load to triage and resolve failures.

It seems to me the problem you bring up would serve an engineering team well to solve and solidify even if the application isn’t running on k8s