I am looking forward to this year’s sockrupcy. Unfortunately, it’s always next month.

I am guessing there were intense negotiations about Observability 3.5

Honeycomb?

Two groups of five plus three

I guess it’s finally settled, then.

So, this?

I draw the line at having to explain for the fifth time that the Vitruvian Man is entirely in the public domain.

Yes but soon the casket will be able to answer

Came here to post this

Also: imagine the bottle callbacks if AWS put out that statement

As the saying goes: “Never attribute to malice that which is adequately explained by incontinence”

Emergency unscheduled cooling

I have an intense need of knowing the weapon of choice. And it might well be “happy little trees”.

I am upping the ante

I was hoping for a “That’s VILE” at the end

So, if JIRA reflect a process that was not designed to be simple and as unobtrusive as possible, the dislike of the process compounds on the dislike of the tool itself.

For JIRA specifically, but I think it applies to CI/CDs in general, there is also the aspect that the product tackles a difficult domain to “make delightful”. They are tools to manage complex, convoluted processes, with very leaky abstractions. And they delegate tons of configuration to end users.

/about/abound/

Edit button when?

There is also a “fashion” aspect to hating things, but it usually grounded in the poor experience in using them. And when you use software that VPs four step removed have bought, you keep the “what were they thinking” to yourself, and hate on the software.