Matt Levine in rare form today on a subject near and dear to my interests which for obvious reasons I cannot go into too much detail about: the UX and human interface design factors of a UI capable of initiating very large wire payments.
If you’ve ever wanted to work at a shop which really cares about the quality of the software their operations professionals use every day, Stripe is hiring.
(I try to avoid that feeling of the hard to spell German word and instead focus on “Here were a group of professionals attempting to do an important thing who were poorly served by their infrastructure. What can we, as a community, learn from this experience.”)
Underappreciated about wires:
1) They’re less dangerous than people believe them to be, particularly domestic wires.
2) Simultaneously, the number of things that have to go wrong between a wire getting cut and a going concern warning for a financial institution is single digits
“Really they’re less dangerous? But they’re generally irreversible?”
What do you take us for, Bitcoiners? No, financial institutions are a high-trust community who are almost never willing to burn multi-decade-or-century reputations for probity over a single client transaction.
A very large mistaken wire normally gets settled by operations professionals on a phone call within a few minutes.
This story stops being an ops story and starts being a legal story when the decisionmakers come to the conclusion “We have a legally colorable claim to this money.”
For similar reasons, if you were hypothetically credited with $100M as a result of a fumble fingered wire, your default assumption should be “You’re going to get a phone call from the bank after they reverse it. Your cooperation is appreciated but absolutely not required.”
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Quoting for endorsement and professional interest.
(With how many companies need to “get developers” it is astonishing to me how few actually do, or who can direct any appreciable amount of creative energy at the task.)
Worth noting that in addition to this unique artwork being a physical instantiation of one’s specific use of GitHub, which is genius, it’s also just “Spend artisan money on developer attention”, which should be math that doesn’t require genius to operate.
It’s more efficient to work with artists if you work with artists frequently than if you do it as a one-off. Art does scale. There are professionals who can be hired to help art scale.
There. Now, just find a piece of art many developers would like to have but haven’t arranged.
There exist many, many geeks who have not yet cottoned onto the fact that they're selling to producers not consumers, and whose natural anchoring to consumer-legible pricing (because its the only pricing they've ever personally paid) drives their pricing grids.
This lasts years.
I really, really want to force everyone to get a quote for office trash removal prior to being allowed to write B2B software pricing.
I've got the update baton again for VaccinateCA.com on Day 33.
We:
* Made several hundred calls throughout the state of California to pharmacies/etc, transcribing what medical professionals said about vaccine availability.
* Added *120* new locations, to total of ~760.
"That sounds like a very high hit rate for a rather scarce vaccine, Patrick."
Indeed it does, second thoughts! Welcome to the magic power of a) lead qualification through use of Eva, our bot which asks a pharmacist one single question to leave the important details to humans and
b) the pedestrian work of having enough surplus call capacity in a day to work through the list of recent Eva leads, which we accomplished with some creativity around tasking, specialization, etc.
* We continued doing the daily keep-the-lights-on work of refreshing old results
* Called hundreds of pharmacies across the state of California asking about vaccine availability and conditions, and wrote down what the pharmacists said.
* Completed preliminary work on our new caller experience, which is Slack- and bespoke-app-based rather than Discord- and Airtable- based. We had heard from our volunteers that, after most were not themselves technologists, the barriers to participation were formidable.
We'll be rolling that out to our volunteer callers over the next few days.
* Continued work on data freshness and strategizing for upcoming changes in society's posture. The vaccine supply is still critically limited, but more doses get delivered almost every day, and this will
I think people underrate the societal importance of us being post-scarcity for basically anything you can buy in a shipping container from 1,000+ manufacturers in, without loss of generality, China.
I broke a dish recently and was mortified, then remembered that human attention about the dish is now much more expensive than the dish itself.
This was not true when I was growing up, surrounded with non-negligible-marginal-cost dishes.
(You can pay more than effectively nothing for a dish, but the thing you're buying is in large part the fact of having paid more than effectively nothing for a dish. The unscarce dishes are perfectly servicable dishes and in many cases actually physically indistinguishable.)
My far less systematic version: "If I need X's cooperation to do Y, and X would give that cooperation to a professional who possessed A, B, and C... is that the minimum possible set of requirements, truly, and could I bet that professional in, say, two $UNITS of determined work."