Join 📚 Josh Beckman's Highlights
A batch of the best highlights from what Josh's read, .
If our notion of “what is supposed to happen” is getting weaker, then developer experience becomes about helping developers and IT teams understand what their software systems are doing in the first place. We can’t see what is supposed to happen, so we need to see what IS happening. This means we need to shift from a mindset and approach of monitoring to a mindset and approach of observing — which in turn suggests that the future of developer experience hinges on better experience of observability.
The Case for 'Developer Experience' - Future
future.a16z.com
AI likes to say vacuous punchy statements like "the final takeaway" or "here's the rub". Then contrastive parallelism "connections, not CPU". Contrastive parallelism should scarcely exist in technical writing, regardless of whether it's AI generated.
Yes, right, if you have a foreign-exchange derivative product that carries “lucrative fees,” that *means* that the customers don’t understand it. (If they understood it, they’d demand lower fees.) If you have a product like that, you will naturally be tempted to sell it to as many customers as possible. And then every so often, something will go wrong, and you’ll have to spend a year or two resisting that temptation and having contrite no-materials meetings with the customers to make them feel better.
Money Stuff: UBS FX Trades Were Too Good
Matt Levine
...catch up on these, and many more highlights
Readwise