Jsone

A lot of dark patterns are opt-in or "We're trying out something new, it's just a test" to start with. Until they're silently upgraded to opt-out a year or two down the line. Then the opt-out gets moved to the ass-end of a legacy settings menu under a generic name under the pretext of UI renewal. Then a couple more years later the "It's been like that for years, what's the issue?" line can be used to shut down anyone who still cares. It's best to nip this kind of thing in the bud.

I have to admit, in my career so far, I've never had to, or seen anyone have to, interact with a commit more than a sprint or two old. Almost all my workplaces enforced the usual standards regarding linear history, squash/rebases before PRs and commit naming, and then did absolutely nothing with the results of that effort. It probably means that I've had an atypical career, but I still wonder if all these ceremonies are as meaningful as we hold them to be.

The article is blocked behind a subscription prompt for me, but it's implemented in a silly way that's trivially by-passable. It's just some js code that checks if you've scrolled past a limit and scrolls you back to the top if so. Anything that removes js from the content defeats it, including Firefox's built-in Reader View.