ChrisArgyle

If you miss Ted Dziuba's writing at Unvoc you will thoroughly enjoy this article

I would have to imagine that a massive corporation like Amazon has automatic detection of issues with tier 1 services like search.

As a Bronx resident this sounds very exciting.

As a jaded consumer of modern media this sounds suspiciously one-sided. What are the downsides? It doesn't seem to generate revenue or lower costs for the city. Why would a politician back this plan?

> While it is technically, theoretically possible that their system is open to the introduction of these biases but does not actually exhibit those biases in the aggregate, it is astoundingly unlikely.

We're in agreement there. A company that is progressive-liberal by nature is going to show some of that bias the company's actions. Even with a conscious effort to avoid bias they'll fall prey to biases they aren't aware of.

I took "systematic bias" to have similar meaning to "systematic error" meaning that there is a constant shift on every data point. Admitting the possibility of bias is very different than admitting bias in every single trending content decision.

Honestly this is more likely due to the actual outcome being too complex for a headline.

"Facebook denies systematic bias but admits their current process allows bad actors to apply bias and takes remediating steps"

Doesn't work. Although WSJ came kinda close.

The central thesis here is that APIs should be treated like GUIs. Make them as intuitive as possible to minimize brain space waste (ie. memorization of non-transferable, vendor-specific knowledge)

Sadly, the post is too short to discuss what "intuitive" means for an API (which could probably fill several volumes).

I'm embarassed to say I haven't even heard of MobaXterm. This is going on my remote-work rig tonight.

That sounds like a scenario for long-form work over a mobile network (eg. on a laptop through a mobile hotspot).

Mosh from a laptop is a no-go for me because there's no Windows-based, full-featured terminal emulator (saved sessions, auth agents, etc) that supports mosh.