Remix.run Logo
LeCompteSftware 2 days ago

Getting back to this....

  The most effective response is rarely to argue the general case. Instead, acknowledge the concern, offer a brief reframe, and propose one concrete demonstration on the person’s own code. Most concerns are resolved by a single successful experience.
First of all, Google didn't have to write this stuff about Kubernetes, suggesting psychological tricks and magic demonstrations to cajole people into agreeing with you. Kubernetes was happy to discuss the general case - I don't like k8s and don't think they had a bulletproof argument, but they offered a pretty good one. What Anthropic is doing here is very very weird. I said "Scientology" earlier and I was not kidding.

Part of the reason LLMs have led me to tear out so much of my own hair is how many people seem to have made it through four years of STEM college without developing any scientific thinking ability whatsoever. A truly stunning number of people have been wowed by "a single successful experience." Actually that section is full of horrible logic:

  Concern
  "I am faster without it."

  Suggested response
  That is likely true for code the person writes routinely. Suggest trying it on the work they tend to avoid: legacy files, unfamiliar services, or test scaffolding, where the leverage is highest.

  Evidence to offer
  Time one tedious task both ways and compare.
This isn't just unscientific and manipulative: it's really goddamn annoying! If someone times me at 1.5 hours reading about and learning an unfamiliar service, and smugly says Claude learned it in 12 seconds of "thinking," either my laptop or a certain Claude Champion is getting thrown out the window.