You just finished a book that argues the best work happens in the open, in writing, where anyone can weigh in. It would be a little awkward to then collect feedback on it through a form nobody else can see.
So this is the feedback channel — a public repository where readers of Open and Async report what's broken, suggest what's missing, ask what's unclear, and share what worked. Same tools the book is about: issues, discussions, and the occasional pull request. Working loudly, applied to the book itself.
You don't need to be a developer, and you don't need to know Git. If you can fill out a form, you can leave feedback.
| I want to… | Go here |
|---|---|
| Report an error — a typo, a broken link, a wrong fact, a formatting glitch | Open an errata report |
| Suggest an idea — a topic that's missing, an example to add, something for the next edition | Open a suggestion |
| Share how you're using it — a win, a quote, a story worth telling | Share a testimonial |
| Ask a question or talk it through — how a practice applies to your team | Start a discussion |
If you're not sure which bucket something falls into, don't overthink it — open an issue and it'll get sorted.
- Errata get triaged, confirmed, and rolled into the next printing and the next ebook update. Corrections credit the person who caught them, unless you'd rather stay anonymous.
- Suggestions stay open as a public backlog for future editions. Others can 👍 the ones they want too.
- Testimonials may show up on the book's site or in promotion — but only the ones where you explicitly grant permission, and only credited the way you asked.
- Everything is public and searchable. That's the point. A future reader with the same question gets the answer for free.
- Order, delivery, or refund problems — those live with wherever you bought the book (Amazon/Kindle, Apple Books, Kobo, etc.); they own the transaction, not this repo.
- Private notes, business inquiries, or press — email press@open-and-async.com.
- Accessibility barriers in any format — email accessibility@open-and-async.com or open an errata report; accessibility issues jump the queue.
By posting here, you grant permission to use your feedback to improve and promote the book — fixing errata, shaping future editions, and, where you've explicitly opted in, quoting you. You keep the rights to your own words; this just lets your feedback do its job. Testimonials are only ever reused when you say yes on the form, credited the way you asked.
Feedback here is public and permanent, so bring the same good faith the book asks of any code review: critique the work, not the person. Participation is covered by the Code of Conduct. Sharp disagreement is welcome — that's how the book gets better. Cruelty isn't.
📖 Haven't read it yet? Open and Async: The collaborative software development playbook for remote and distributed teams — by Ben Balter.