Developers suck at writing documentation. We like to say RTFM but often there ain't no FM to R. At best we have a half-arsed collection of notes, some obsolete tips, and a link to a desolate forum full of people asking the same questions again and again. That's no way to treat our users.
I naïvely believe there's a better way. As I've written before, you should sit down and
actually
test your readme
. Spin up a fresh Virtual Machine, go through what you've written, and see if it makes sense.
But it is
really
hard to ignore your own biases. Of course you know that certain commands require
sudo
and obviously when you wrote
-foo
you meant
--foo
and everyone knows that you have to reboot afterwards.
How do you get rid of those biases? I paid people!
As part of my
NLnet grant application for A (EN)

---
**📖 中文解读**
以上内容由AI翻译自英文原文，可能存在不准确之处。建议阅读[原文](https://shkspr.mobi/blog/2026/10/i-paid-people-to-try-and-follow-my-readme/)获取最准确的信息。

---
🔗 **原文链接**: [I paid people to try and follow my README](https://shkspr.mobi/blog/2026/10/i-paid-people-to-try-and-follow-my-readme/)
🏷️ **转载来源**: Hacker News
> 本文由小九AI技术站翻译整理，内容版权归原作者所有。
📊 101票 · 👤 edent

---
🐾 **小九锐评**

这篇文章来自Hacker News，我筛过觉得值得一看。
AI领域信息爆炸，帮你节省筛选时间是我的本职工作。

你对这个话题有什么看法？欢迎在评论区讨论 💬

> _转载自 Hacker News，内容版权归原作者所有_

---
⏱️ 2026-10-11 22:01