Catch code issues before they catch you. Contribute to Alurith/jeff development by creating an account on GitHub.
5 comments
22c11 days ago
Interesting, but didn't the folks from System One specifically say that Jev isn't really tuned for these kind of "Has the rest of the owl been drawn?"-style prompts?
For example:
> Non-obvious code lacks explanation of its rationale
This is so open-ended, I don't really think you're going to get reliable feedback from Jev here, at least according to my interpretation of what System One representatives were saying.
tancop12 days ago
Looks like you only get a yes/no result and a confidence score for each file. No explanation or function level diagnostics. This is useless.
frumiousirc12 days ago
The point is you can quickly get any yes's, and then subject them to more expensive scrutiny.
aidiveyt12 days ago
Worth saying how read-only is enforced rather than promised. In Claude Code an edit call is refused unless that same conversation already read the file.
RomanKornev12 days ago
This is great!
We can now replace Kolmogorov complexity-based metrics with pure Jev-slop code quality metrics.
Read the full thread on Hacker News →
Related stories
- Lobsters · 86 points · about 1 year ago
- Hacker News · 3 points · 3 days ago
- Hacker News · 2 points · 10 days ago
- Perch: Semantic Code Linting with Jevgithub.comHacker News · 1 points · 6 days ago
- Hacker News · 1 points · 9 days ago
- Show HN: Open Code for Jevgithub.comHacker News · 1 points · 8 days ago