2,349 karma · joined September 6, 2018
Avoid making mistakes that harm others. Be aware that you will make some anyway, and you won’t always recognise them as mistakes at the time. (If you take pride in having a spotless record, you’re liable to deceive yourself.) And when, on reflection, you realise you have harmed someone by mistake, figure out what you can do to 1) fix the harm and 2) prevent it happening again. And then tell them this plan in a way that commits you to it. That’s an apology. This way you make fewer and fewer harmful mistakes over time. The idea that someone can just “avoid mistakes in the first place” to avoid needing to apologise is dangerously lacking in humility, in my opinion.
This is just slimy sales tactics. The level of ‘acceptable to most people’ swings back and forth. It’s not a slippery slope.
But what does any of this have to do with my question? Are you really suggesting that attempts to regulate the prescription of puberty blockers in children are a veiled attack on trans people? And you’re saying this to defend the claim that trans people are regularly being ‘told’ they shouldn’t exist?
Who does this? I'm asking because I have seen this notion expressed hundreds of times, but in 100% of cases, there is no example given that even remotely justifies this hyperbole.
BUT: I didn't read the whole article. I read kogepathic's comment first, which gave away the twist and framed the headline as clickbait, and I went along with that. But I now see it's as you say. Lesson learned.
I definitely don't think that writing an intriguing headline and delivering on it with a satisfying story counts as clickbait. Clickbait is something that fails to deliver at all, not something that delivers in a way you didn’t expect.
EDIT: I've had my faith restored. Added reply to a comment below.
Markets are powered by billions of instances of “what someone wants” but that doesn’t mean the resulting market movements are always a good indicator of what everyone wants as an environment. Sometimes aggregate human activity results in a crappy experience for most participants. “The market has spoken” is a glib, ideological phrase that can be used to dismiss any discussion about ways we could steer and improve markets to make them do a better job at facilitating human happiness and flourishing.
If someone ever brings me evidence that having stronger grip does not help you avoid falls, then (a) that would be surprising and interesting, and (b) I wouldn't feel like a fool for having improved my grip strength anyway.
Empirically proving causation is often difficult or impossible. It's irrational to expect every potentially useful idea to meet that high bar before taking it into consideration. If someone is trying to sell me something, or if the idea goes against common sense, I'll demand proof, but that's not the case here.
With “How” in the title, it comes across as what it is: a light popsci/lifestyle piece that should be taken with a grain of salt, but might still contain interesting food for thought/discussion.
Deno’s vendoring approach isn’t like a stopgap in case third party servers go down. It’s the ’right’ way in Deno, and is another brilliant fix to Node’s approach.
Node always makes you go through a formal step to install a dependency - and then you’re still reliant on npm’s CDN being online during your builds anyway. The only way to break that build time dependency is to use a clunky, nonstandard hack to check in your node_modules, like yarn 2.0 or pnpm, which then takes you right off Node’s “golden path” (such as it is) and creates loads of incompatibilities.
Deno’s approach is the best of both worlds.
1. With Deno you can import direct from a URL with no formal install step, which is great for prototyping. The caching engine makes it fast without a need for every little toy project to have to have a giant node_modules folder.
2. Vendoring your scripts provides a dead easy, golden-path way to make your project completely non-dependent on third party during build, ie gives you same advantage as using Yarn 2 or pnpm in Node, but as a first class citizen of the runtime, so it’s efficient and standardised and will therefore not have tons of ecosystem incompatibilities.
I tried to get into MobX years ago but found it impossible to get along with. I don’t know what it’s like now, but the documentation back then failed to explain the magic. It was just like “Hey, look how convenient this is, just follow our instructions and you’ll be fine (and don’t think about how it works)”.
Then some time later React came out with hooks, and they took the time to introduce the concept carefully, to explain how it’s actually really weird and non-idiomatic and principle-breaking but leads to all these ergonomic benefits, just make sure you understand the weirdness and keep it contained. They give you the information you need to change it in your head from ‘magic’ to ‘smart compromise’.
Interesting, how do you know about this? I was under the impression GitHub were still mostly happy with Rails.