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
Yes, it would be great if everyone did fully reproducible science and made all their data available and *actually responded* when you asked them questions and got a pony. But in the current, *actual* world, *most* papers are missing important details. The problem of having to scan your eyeballs past a few extra digits is a silly non-issue compared to the problem of meaningless results everywhere. So please stop spending your energy actively trying to convince people to delete one of the very few error correction methods that we *actually have* and that *actually sort of works*.
Please Show Lots of Digits
DYNOMIGHT
Sometimes people use "respect" to mean "treating someone like a person" and sometimes they use "respect" to mean "treating someone like an authority"
and sometimes people who are used to being treated like an authority say "if you won't respect me I won't respect you" and they mean "if you won't treat me like an authority I won't treat you like a person"
and they think they're being fair but they aren't, and it's not okay.
The Respect of Personhood vs the Respect of Authority
Jason Kottke
...catch up on these, and many more highlights
Readwise