There are already plenty of studies available to be found.

If your arms are resting, then your fingers and wrists are doing the maximum amount of reaching as you type. If you use a wrist rest you are encouraging your fingers/wrist to reach up (bend in your wrist) instead of neutral or reaching down (more natural position).

"Surfacing the best comments" is only a problem at scale. And attention media demands scale whereas your social circles break down at scale. Commerce sites (like Yelp or Amazon) also demand scale, so they also have a "surfacing the best" mechanism.

Cold cases might get reopened because of advances in technology or other changes over time.

But I also much prefer my EV BMW to my previous Teslas. Nicer to drive, nicer features (better sound, HUD, sunroof), hardware controls, door handles that you can open with either hand, better in weather (no rain in the trunk).

My family complains the i4 has a smaller cabin, but the driver's seat feels just fine to me. :D

Knowing and using etiquette is often more effective.

JD Power and Consumer Reports both rate BMW above average.

BTW, my impression of BMW maintenance from prior decades is expensive and not great reliability. I care about it less now with EVs because there is so much less regular maintenance. No oil changes, no brake pad changes, etc.

It's still true that: alcohol is a very good way to destroy the old glossy screens.

Some oft-cited examples are curb cuts (the sloped ramps cut into curbs for sidewalk access) and closed-captioning (useful in noisy bars or at home with a sleeping baby).

There are many examples from the web where designing with constraints can lead to broadly more usable sites- from faster loading times (mobile or otherwise) to semantic markup for readers, etc.

But then I tried it and...WHAT?! Git is an endless rabbit hole of complexity.

I love using IJ + git because there are no seams in between edit and commit. For instance, with IJ, I could easily split every other line of a change into separate commits.

Maybe there's a way in git to stage only certain parts of a diff, but I'd have to go an learn another flag or command that I'm going to forget by the next time I need to do it again.

Also with IJ, I just glance at my main branch tab and the highlighting tells me what commits aren't in my checked out feature branch.

Two small examples but there are many more and it adds up.

You might start with a basic timeline of what happened, then you'd start exploring: why did this change affect so many customers (this would be a line of questioning to find a potential root cause), why did it take so long to discover or recover (this might be multiple lines of questioning), etc.

Beyond that: separating into change lists (staging changes by line inside a file) and the graphical presentation and filtering of the commit history (highlighting what commits are in/out of your branch, show the git history of a section or line of code, show repo files at a commit)

Submarines sail because they are nautical vessels. Wind-up bathtub swimmers swim, because they look like they are swimming.

Neither are animate objects.

In a browser, if you click a button and it takes a while to load, your phone is thinking.

Are you sure there aren't certain people driving these "informal" parties?

;)