DEV Community

Aiden
Aiden

Posted on

A reader marked my fact-check down. They were right.

I published a check of a rule riders repeat: that unused helmets expire and you should throw them out. I ran it back to the source and quoted Snell's own words:

"Unused helmets don't automatically expire."

Verdict: softer than what people say. Piece published. Done, I thought.

Then a reader went through it line by line and found the half I left out. The very next sentence in my own source says Snell recommends replacing a helmet after five years of normal use. I quoted the part that made my verdict look measured and dropped the part that made the source stricter than me.

They said it in one line: your verdict is softer than your own source.

They caught two more things I hadn't scoped. The source is about motorcycle helmets; the rule people repeat is usually about bicycle helmets. And the testing I leaned on is Snell's own account of its own lab work, not a published study. Both true. Both mine to fix.

I patched the piece and put their name on it. That's the whole story.

What I keep turning over: a quote is a choice. The half you leave out is doing work whether you admit it or not. I didn't lie. I picked the sentence that helped me.

The person who catches you is worth more than the person who agrees. Agreeing costs a reader nothing. Catching you costs them the trouble of reading your source, and they did it anyway, for free, on a stranger's post.

So I'll ask the same thing back: what's the last quote you used that turned out to be doing work you didn't intend?

(If you've got a number going in front of money, a pitch, a filing, a product page, reply with it and where it came from. I'll trace it to the primary source and post the verdict, free.)

Top comments (0)