Principle

You Can't Read Your Way to Conviction

David Heinemeier Hansson's claim that conviction about a new technology comes from handling it yourself, not from reading accounts of other people handling it.

Pointers, not performance

David Heinemeier Hansson's formulation comes directly out of his own reversal on artificial intelligence: so much of the ability to actually move an opinion, in his account, comes not from abstract argument but from touching things, setting a tool up, using it badly for a while, and slowly developing a feel for where it is heading.1 His analogy is precise about what reading a write-up actually gives someone, which is why it holds up: "You can read a write-up of anyone else using something, but it's kind of like trying to learn to drive a race car by reading a book about it. You could pick up some pointers, but until you get behind the wheel it's not going to internalize." He is careful not to claim reading is useless, only that it produces pointers rather than performance, meaning a person can hold entirely accurate propositions about a technology and still have no actual ability to act on them, because the operative knowledge involved is tacit rather than propositional.

Nerd-sniping as the persuasion method

The mechanism by which Tobias Lütke changed Hansson's mind is worth extracting on its own, since it functions as a technique rather than as an argument. Lütke never made a direct case for AI at all. He simply kept saying "look at this, look at this, look at this," which produced not agreement but an intolerable status condition: "I cannot be the person in this relationship who's not up to date on this shit."1 Hansson calls this being nerd-sniped, and the sequence is the interesting part: social discomfort with a respected peer produced the action of actually installing and trying the tools, and that action, not any argument, is what produced the eventual conviction. The missing input the whole time was never information, since Hansson already had access to plenty of accurate descriptions of what the tools could do.

Why it matters

The claim invalidates a fairly common research posture, since diligently reading the literature on a fast-moving technology, however carefully done, does not by itself produce the ability to judge it well. It also offers an explanation for why domain experts frequently underrate a shift they are well positioned to see coming: an expert's early dismissal is often based on real, accurate observation of what a technology currently is, and being right about the artifact while wrong about its trajectory is the standard failure mode, correctable only by sustained hands-on contact. It sets a fairly demanding bar for any stated technology opinion, since the useful question about someone's take is not what they have read but what they have actually run themselves. And it grants peer relationships a genuinely epistemic function rather than only a social one, since Hansson's own conviction here is downstream of a single friendship rather than of any argument.

Tensions

The approach does not scale, since nobody can personally handle every technology that plausibly matters, which means most positions necessarily have to be held on secondhand evidence, and no allocation rule is offered for which topics actually earn the hands-on time. Contact also produces conviction rather than correctness on its own: Hansson got hands-on with AI tools and arrived at a position that agents make software worse by default unless deliberately constrained, which is roughly the opposite conclusion from Lütke's, despite Lütke being at least as hands-on with the same tools, so touching the technology gave both men confidence without converging their views.1 Nerd-sniping as a method also appears to require a specific kind of relationship, since it worked here because Lütke is a peer Hansson respects and spends time with outside of work, and it is not obvious the same social-status mechanism transfers cleanly to organizational settings where status differences between people are less equal.

Practiced by

Connections

Loading connections…

References

  1. 01

    DHH: How to Build a Profitable Company Without Losing Control

    David Heinemeier Hansson · podcast · 2026

Related