Almad

That's from the good old days where truth mattered. Like how many action movies are about "getting the truth out" where that act in itself brings consequences, cut, happy ending?

Compare with now: revolution may be televised, but its spread not amplified and its authenticity denied. And if you have sufficient tribalism, it will not make a dent.

From what I know, politologists are analyzing the situation in US from a perspective of "mid intensity civil war".

So what you're writing is aligned with tactics you'd expect...?

So what are the sources for people driven insane by it?

(I have no opinion, but find it mildly suspicious given that I happen to sometimes drive through Germany, and the country seems to be currently less insane than, say, US)

> Gradle files (worst abomination of a build system ever)

Ant? Maven?

Not always. You may also end up with having incompatible set of ciphers (happened to me).

"Get off my Internet lawn if you can't be up to date" is what we're saying and I just do wonder whether we haven't exchanged too much of accessibility for too little of security.

Internet starts to have 1y memory retention.

Unless refreshed by active learning, aka someone doing the refresh job.

Or unless delegating the work to large players—either the memory or the hosting.

EDIT: This feels wrong, even when done for right reasons. And I wonder whether this would fly without LE and whether this means we are officially making LE THE critical part of Internet infrastructure.

I'd say quite the opposite. What you say is one of the myriad of considerations that should go into prioritization by the team, yet is super hard to capture by any hard attribute as I believe the "positive/negative mental health effect" is way more complicated than "bug/feature", yet known by the team.

One of the reasons I am delaying design is getting deeper into accessibility and readability research. And I have decided to write some content first ;)

If you mean how to prevent them, well, no bugs so no way to create them.

If you mean how they handle them, there is an incident procedure for that. If it's not really an incident but, well, I need this next week for Gartner Magic Quadrant...I have phone numbers of managers in my reporting chain.

In both companies I've been using that, it was a very simple RT/JIRA-SD-style system: "open a subject/text ticket, clock starts ticking, on call engineer gets a non-wake-up memo and will reply with high priority during work hours" and ticket will get closed ASAP and we do achieve inbox 0 regularly.

Yes, there are obvious issues and it requires two things to work:

1) If you actually have no clue about the product, you are respectfully told to fuck off to normal user support channel 2) If you keep misusing this for user support / slack channel, you get your access revoked.

...which are hard sells in large companies, of course—on the other hand, in BigCo I got success in getting an engineering headcount to accommodate that.

True. I think one of the issues is slapping an issue tracking system on a bunch of different problems.

As mentioned, this is true for versioned software, not for continuously deployed SaaS.