drob

5 ms·

1.
by drob 9d ago
Sometimes, but I think there are a few problems with this: 1. Some context doesn't have an obvious place to write it in the code. If you're explaining why a tricky function is implemented a certain way, you can leave the explanati
2.
by drob 9d ago
We should publish some stats. The fix rates on bugs are around 45% baseline, increasing over time as we learn from behavior within a given codebase. The merge rates for the codebase health work we do (e.g. deleting dead code) are very high,
3.
by drob 9d ago
Agreed that domain experts should be making these kinds of decisions, and the right way for an agent mistake to get caught is going to depend a lot on the cost and probability of the mistake. My only point here is that the agent side of the
4.
by drob 9d ago
Author here, hello! Happy to expand on how we're thinking about this if any of it is unclear. We wrote this post as part of a launch, which you can check out here: https://x.com/danlovesproofs/status/209518218
5.
What kinds of bugs does AI generate?(blog.detail.dev)
5 points by drob 3mo ago|4 comments
6.
Benchmarking a Bug Scanner(blog.detail.dev)
17 points by drob 5mo ago|9 comments
7.
by drob 10mo ago
Should work fine. Ping me dan@detail.dev or @danlovesproofs with your account info so we can look into it?
8.
by drob 10mo ago
We've been thinking about this too. We have some ideas. Thanks for the comment, in any case – gave us a lot to chew on.
9.
by drob 10mo ago
Other auth providers for sure. We'll be adding shortly. Using an alternate auth provider won't even prevent you from scanning non-public GitHub code. There's a GitHub OAuth App just for auth (which is what you're seeing
10.
by drob 10mo ago
As far as we can tell this is a github-ism, and any OAuth permission is a form of "acting on your behalf": https://dappling.medium.com/a-github-app-would-like-to-act-o...
11.
by drob 10mo ago
Hi bflesch, fair point – our About Us page has a lot about what we think and not about... us! I'm the founder. Previously I was at Heap for nine years. There's a company LinkedIn with the rest of the team: https://www.l
12.
by drob 10mo ago
We've run it on a few firmware repos and gotten good results. A lot of firmware code tends to have really poor type-safety which means lots of low-hanging bugs. We should be able to handle cross-compilation. Want to try it? Ping me in
13.
by drob 10mo ago
Just github for now, but purely for reasons of plumbing. We'll add gitlab and others. We support java, c/c++, kotlin, ruby, and swift as well. Did you have something specific in mind?
14.
by drob 10mo ago
Github only for now. Out of curiosity, is yours on gitlab? Something else? We should be able to find something interesting in most codebases, as long as there's some plausible way to build and test the code and the codebase is big enou
15.
by drob 10mo ago
Fix is deploying, sorry about that!
16.
Show HN: Detail, a Bug Finder(detail.dev)
67 points by drob 10mo ago|28 comments
17.
by drob 2y ago
Fwiw, the authors never actually claimed this. From their technical report [0]: > Chai-1 achieves a ligand RMSD success rate of 77%, which is comparable to the 76% achieved by AlphaFold3 [0] https://chaiassets.com/chai-1&
18.
by drob 2y ago
On a personal level I can absolutely empathize, but respectfully, I don't see why that should be the state's concern. The goal of IP law should be to promote the creation of good art, not to make sure artists' wishes are resp
19.
by drob 2y ago
Do bad adaptations prevent good adaptations? Lynch's Dune flopped but Villeneuve had a $165m budget. We can't know the contrapositive but I don't see why giving the author a veto makes good outcomes more likely, especially de
20.
by drob 2y ago
He owns the IP, but we all lose out from this system. Art has asymmetric upside – bad art doesn't really harm anyone (usually just gets forgotten) but good art enriches millions of people's lives. It might have been amazing. It mi
21.
by drob 5y ago
Zstandard gets us 5.5x compression. The previous ZFS config got us 4.4x compression. XFS, which we ran on for years before rolling out ZFS, does not compress.
22.
Hiring for expertise you don't have(heap.io)
2 points by drob 5y ago|0 comments
23.
Don't do a hack week; do a ship week(heap.io)
1 points by drob 5y ago|0 comments
24.
Pseudo-R²: A Metric for Quantifying Interestingness(heap.io)
4 points by drob 5y ago|2 comments
25.
by drob 5y ago
Fixed, thank you for flagging!
26.
Accidentally exponential behavior in Spark(heap.io)
75 points by drob 5y ago|33 comments
27.
Query Optimization in Postgres with Pg_stat_statements(info.crunchydata.com)
4 points by drob 6y ago|0 comments
28.
Applying Textbook Data Structures for Real Life Wins(heap.io)
157 points by drob 6y ago|32 comments
29.
by drob 6y ago
Fixed. Thank you again for flagging!
30.
by drob 6y ago
Ah. Yup, it is. Thank you for flagging. Will fix this.

More ›