Free MIT tool lets beta readers voice feedback pinned directly to manuscript passages

·1 views

A free, open-source tool called Beta Reader has been released under the MIT license to streamline manuscript feedback collection. Instead of written notes, readers listen to a text-to-speech rendering of a manuscript, tap any passage, and record spoken or typed reactions in real time. Each reader's notes are automatically committed to a dedicated branch in the author's GitHub repository, with no accounts, databases, or build steps required. The tool consists of a single HTML file and a Cloudflare Worker, and is designed to be set up via AI coding assistants like Claude Code or Cursor using an included AGENTS.md guide. The project is publicly available on GitHub and was created by The Fort That Holds.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Kindy AI Avatar Guides Non-Cash Volunteers to Local Giving Opportunities

A developer built Kindy, a voice-driven animated AI companion, as part of a Weekend Generosity Challenge to help people contribute without donating money. Users speak naturally to a 2D cartoon avatar that responds with exaggerated comic emotions and personalized suggestions based on their skills, interests, and available time. Kindy then generates six actionable volunteering ideas and uses Google Maps to surface nearby community centers, food banks, and volunteer spots. The app is powered by Google Gemini AI models for conversation and text-to-speech, with a React frontend handling real-time avatar expressions via SVG animations. It is deployed on Google Cloud Run, with full source code available on GitHub and no user data stored externally.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Dev Team Shipped Slower Parallel Feature After Benchmark Showed 16% Performance Loss

A developer building logq, a command-line log query tool for a zero-dependency hackathon, added an 8-goroutine parallelization flag despite benchmarks showing it ran 16% slower than a single worker on a 76.3MB test file. The team disclosed the performance gap immediately and shipped the feature regardless, citing its potential value at larger scales. A key design decision was a three-valued evaluator distinguishing between MISSING, null, and false states, preventing query crashes when log records have inconsistent shapes. The project also replaced the widely used third-party library tidwall/gjson with roughly 150 lines of custom code built on Go's standard library, avoiding known issues with float64 precision loss and unpredictable map iteration order. The team removed a CI pipeline two days before submission after it failed for reasons they could not fully diagnose, choosing transparency over leaving an unexplained failure badge.

0 comments Read more at DEV Community

ProgrammingHacker News ·

Ponytail: Lazy Senior Engineer Skill

Article URL: https://ponytail.dev/ Comments URL: https://news.ycombinator.com/item?id=49592706 Points: 17 # Comments: 8

0 comments Read more at Hacker News

ProgrammingDEV Community ·

Developer finds npm warnings, CI glob quirks, and registry surprises shipping tiny package

A developer publishing a 200-line npm package called video-bitrate-calculator encountered three misleading tooling issues during the release process. An npm warning claimed CLI entry points were deleted during publish, but reading npm's own source code revealed the paths were merely normalized and the entries remained intact. In CI testing, quoted glob patterns in the test script worked on Node 22 but silently matched nothing on Node 18 and 20, meaning newer Node versions masked a real coverage gap rather than catching it. The fix was to drop the glob entirely and let the Node test runner discover test files automatically, ensuring consistent behavior across versions. A third surprise involved npm login unexpectedly opening a signup page for an unfamiliar registry, highlighting how default tooling assumptions can mislead developers into unnecessary or incorrect actions.

0 comments Read more at DEV Community