Ebook Reviewer Wanted: Help Me Find What’s Gone Stale
Three things this does that prose doesn’t.
It forces specificity. You can’t write a row without naming a location, so vague impressions get filtered out before they reach me.
It separates severity from opinion. “Outdated” and “Broken” are different problems with different urgency. A prose paragraph blends them together and I have to guess which is which.
It converts directly into work. A filled-in sheet is already a to-fix list. I sort by status, work top to bottom, and reply to each row. Nothing gets lost in a thread.
If you ever run a review process — for docs, a spec, a design, a codebase — some version of this table will serve you better than asking for thoughts.
Who I’m looking for
Anyone who writes code. That’s the entire filter.
Seniority helps for some books and actively hurts for others. If you’re three months into PHP and a chapter loses you, that’s the single most useful signal I can get — I wrote it for you, and it didn’t land. A senior engineer will read straight past the same gap because they can fill it from experience without noticing they’re doing it.
The one thing I do need is bluntness. If a chapter is weak, I need you to write “this chapter is weak” rather than “this chapter has potential.” I’m not sentimental about any of it. If a section should be cut entirely, say so and I’ll cut it.
Reviewers who tell me it’s all great are, with respect, not useful to me.
What you get
The full series. Not just the book you review — all of it, free, permanently.
Your name in the acknowledgements. Printed in every copy of the new edition, under whatever handle you choose.
Let me be honest about the exchange: reading a technical book carefully takes somewhere between four and eight hours depending on which one you pick. What I think does cover it is early access to the whole series, a permanent credit, and — if you’re the kind of person who enjoys this — a few hours of deliberate close reading in your own field, which is not the worst way to spend a weekend.
Timeline
| 26 July | Applications close |
| 2 August | Reviewers selected and books assigned |
| 3 – 24 August | Review window |
| Late August | Final edition ships |
Three weeks for the review itself. You can break it up however you like — nobody expects a single sitting.
Applying
The form takes about a minute. You’ll pick which book you want, tell me roughly where your experience sits, and give me the handle you want in the acknowledgements.
Applications close Sunday, 26 July.
Fuente: Artículo original