A blogger begs you to leave a comment — on a blog with no comment box
Jake Worth's post argues you should always leave something behind online: a comment, an upvote, a 'this worked'. The thread's first reply pointed out his own page had nowhere to do it.
The argument is small and practical: thousands read, almost no one replies, and a one-line trace surfaces good answers, repays invisible labor, and builds a searchable index of your own learning.
The thread answered in kind, leaving traces about traces. One engineer once upvoted a Stack Overflow answer that fixed his bug — only to be told he couldn't upvote his own post from years earlier.
The argument: spend ten seconds, leave something behind
Jake Worth's post makes a modest case with three legs. When something online helps you — a blog post, a forum answer, a tool you're abandoning — leave a small signal: a comment, an upvote, a "this worked," or honest feedback on why you're walking away. His reasons: it adds humanity to an isolating internet, since most creators publish into a vacuum; it surfaces quality answers for the next searcher; and it builds your own "learning exhaust" — a commented and upvoted history that becomes a personal, searchable index of what helped you. His own data point: the blog draws thousands of readers a month, and direct feedback is a tiny fraction of that.
The reply the post wrote itself into
The thread's sharpest beat was structural. A post pleading for feedback offered no way to give it on the page:
"If you don't have any comment box it's hard to give you any feedback." — a high-karma commenter
Readers noticed and complied anyway, several explicitly noting they were leaving the trace here because there was nowhere there: "There was nowhere to comment," "Left this comment as a trace." The irony became the discussion.
The best traces are the ones you leave for yourself
The most-loved replies turned the idea inward — the trace as a gift to your future self. One was a small perfect loop:
"I was stuck on a tricky JS bug… ended up on a decent answer on StackOverflow. It worked! I went back to upvote it, and it said 'You can't upvote your own answer.' Yes, it was my own answer from years back." — an engineer running a privacy-friendly analytics product
Another demonstrated the "searchable index" claim live — recovering a half-remembered comment through his own upvote history:
"I wished I'd commented so I could find it again… then I thought, maybe HN tracks upvotes too, and sure enough it does, I was able to find the comment." — a developer who tested the idea mid-comment
The cost of leaving a trace
Not every trace is welcome. One reader followed the post's advice to tell a maker why their tool failed — and regretted it:
"'Tell them it didn't work and why.' I did that, once, and got an expletive-filled rant about ungrateful, entitled shits in response. These days, I just quietly slip out the back." — a software engineer in New York
A quieter counterpoint came from the trail: on the Pacific Crest Trail the rule is the opposite — leave no trace, out of respect for nature and others. Online the cost of a trace is near zero and the upside compounds; offline it's the reverse. Worth's post is really an argument that the internet has the trail's etiquette backwards. The thread, by leaving hundreds of traces about leaving traces, mostly agreed — and the missing comment box did more to prove his point than any paragraph could.
Get breakdowns like this every day
The top Hacker News stories, unpacked — by email, Telegram, or RSS.
He spent two years building a giant motorised banana, then drove it across a continent
Steve Braithwaite's two-line life plan: build a huge motorised banana (done), drive it around the world (working on it). The HN thread's recurring worry wasn't the engineering, it was how often US police pull the banana over.