d-yoda

7 ms·

1.
AI coding agent PR merge rates: Claude 84%, Codex 74%, Devin 43%, humans 85%(arxiv.org)
1 points by d-yoda 13d ago|0 comments
2.
Models Write Messier Code Than the Human Who Fixed the Same Bug(codescan.dev)
2 points by d-yoda 2mo ago|0 comments
3.
by d-yoda 2mo ago
Anthropic would say that's exactly why they're in the red.
4.
by d-yoda 2mo ago
That's awesome!
5.
by d-yoda 2mo ago
How is the collateral handled? Is it like the agent borrows from platforms such as AAVE or Morpho?
6.
by d-yoda 2mo ago
I have never experienced a situation like this, so I can only assume there is a problem with the harness or something...
7.
by d-yoda 2mo ago
I think it would be better to have support for Skills.
8.
by d-yoda 2mo ago
I feel the pool is often way more fascinating than the actual front-pages nowadays.
9.
by d-yoda 2mo ago
So it’s basically similar to .onion on Tor Browser, but without requiring a blockchain. The idea sounds interesting. If you can find strong use cases for it, it could be very promising. (Monetizing OSS is always difficult.)
10.
by d-yoda 2mo ago
Isn't high quality defined by how easy it is to maintain as the scale grows? I feel there is a disconnect between the "quality as perceived by developers" and the "quality as experienced by designers and users."
11.
by d-yoda 3mo ago
I agree with most of this. I think code quality has been improving though. Compared to a year ago, the difference is pretty noticeable. I ran into many of the same issues, and they motivated me to experiment with a linter that flags duplica
12.
by d-yoda 8mo ago
Hi HN. I built a CLI to install skills for AI coding agents from GitHub. Supports 30+ agents including Claude Code, Cursor, and Copilot. Feedback welcome.
13.
Show HN: A Python CLI for Managing AI Agent Skills(github.com)
1 points by d-yoda 8mo ago|1 comments
14.
by d-yoda 8mo ago
I recently reviewed some code written by a non-engineer using Cursor's vibe coding. It was full of dead code and patchwork logic. Vibe coding can build a working prototype, but maintaining it? That's another story. So I built a Gi
15.
Show HN: Weekly code audits for vibe coders(pyscn.ludo-tech.org)
1 points by d-yoda 8mo ago|1 comments
16.
by d-yoda 9mo ago
I built a GitHub App that monitors your Python codebase for quality issues. It reviews PRs and runs weekly audits on the entire repo. When it finds problems, it posts them as comments or Issues with concrete suggestions. I open-sourced pysc
17.
Show HN: An AI agent that audits your entire Python codebase(pyscn.ludo-tech.org)
2 points by d-yoda 9mo ago|1 comments
18.
by d-yoda 9mo ago
So what happens when they swap Claude for Llama under the hood?
19.
by d-yoda 11mo ago
Thanks! I will fix the issue as soon as I can in the next version.
20.
by d-yoda 11mo ago
Yes, that's definitely something I'm looking into. I've received a few comments about AI coding integrations, so it's becoming a high priority.
21.
by d-yoda 11mo ago
This is super insightful, thank you for sharing. It's a great list of common LLM-generated anti-patterns. I'd love to look into incorporating checks for these into pyscn. This is exactly the kind of stuff I want it to catch.
22.
by d-yoda 11mo ago
Wow, was it really in some newsletters? That's awesome to hear, and would definitely explain the recent spike on GitHub! Thanks a lot for the bug report and for providing the details. I have a hunch—it's possible that you need to
23.
by d-yoda 1y ago
Thanks for trying it out! For the progress bar bug, would you mind opening a GitHub issue with details? That'll help us track it down. Great idea using it as grounding for AI-assisted refactoring! Let us know how that workflow goes.
24.
by d-yoda 1y ago
Haha, maybe your code is better than you think! But seriously, we'd love to hear if the thresholds feel too lenient. Feedback welcome!
25.
by d-yoda 1y ago
Thanks for sharing! Good to know about rust-code-analysis. Always helpful to see what other tools are doing in this space.
26.
by d-yoda 1y ago
Fair point! My initial target was engineers using AI, but I'm open to refining the messaging.
27.
by d-yoda 1y ago
MCP integration could be a good option. If there's interest, feel free to raise an issue on GitHub.
28.
by d-yoda 1y ago
Pylint's duplication check is text-based (compares lines), while pyscn uses tree edit distance on ASTs. This means pyscn can catch structural clones even when variable/function names differ.
29.
by d-yoda 1y ago
They complement each other - Ruff for style, pyscn for architecture. pyscn focuses on structural quality - checking if your code follows fundamental design principles like DRY, YAGNI, or other best practices.
30.
by d-yoda 1y ago
Rust is definitely the king of performance! I personally love Go, but Rust's performance is truly impressive.

More ›