logoalt Hacker News

chillacyyesterday at 8:56 PM1 replyview on HN

Boris has been very open about the 100% AI code writing rate and my own experience matches. If you have a typescript or common codebase, once you set your processes up correctly (you have tests / verification, you have a CLAUDE or AGENTS.md that you always add learnings to, you add skill files as you find repeatable tasks, you have automated code review), its not hard to achieve this.

Then the human touch points become coming up with what to build, reviewing the eng plans of the AI, and increasingly light code review of the underlying code, focusing on overall architectural decisions and only occasionally intervening to clean things up (again with AI)


Replies

giancarlostoroyesterday at 10:18 PM

I'm aware I've been building my own alternative to Beads for weeks now. the instructions.md file and something like Beads is epic.

https://github.com/Giancarlos/guardrails

I didnt like how married to git hooks beads was, so I made my own thats primarily a SQLite workhorse. Been using it just the same as I have used Beads, works just as good, drastically less code. I added a concept called "gates" to stop the AI model from just closing tasks without any testing or validation (human or otherwise) because it was another pain point for me with Beads.

I fully sync the issues to GitHub to boot.

https://github.com/Giancarlos/guardrails/issues

Works both ways, to GitHub, from GitHub. When you claim a task, its supposed to update on GitHub too (though looking at the last one I claimed, doesnt seem to be 100% foolproof yet).

show 1 reply