dakshgupta

10 ms·

1.
by dakshgupta 3mo ago
Apart from the job-related stuff others have already said, there is a bit of novelty/bragging rights in landing a PR into a major open source project.
2.
PR spam today looks like email spam in the early 2000s(greptile.com)
265 points by dakshgupta 3mo ago|155 comments
3.
by dakshgupta 3mo ago
Not yet - but we want to do this. Similarly true for the ephemeral unit tests that greptile writes.
4.
TREX: An AI code reviewer that runs your code(greptile.com)
60 points by dakshgupta 3mo ago|11 comments
5.
Slop is not necessarily the future(greptile.com)
305 points by dakshgupta 6mo ago|484 comments
6.
by dakshgupta 8mo ago
The signal-to-noise ratio problem is unexpectedly difficult. We wrote about our approach to it some time ago here - https://www.greptile.com/blog/make-llms-shut-up Much has changed on our approach since then, so we&#x2
7.
by dakshgupta 8mo ago
Thanks! We go over that on many other pages. Here are some: https://www.greptile.com/benchmarks https://www.greptile.com/greptile-vs-coderabbit https://www.greptile.com/greptile-vs-bugbot
8.
by dakshgupta 8mo ago
I agree that none perform _super_ well. I would argue they go far beyond linters now, which was perhaps not true even nine months ago. To the degree you consider this to be evidence, in the last 7 days, the authors of a PR has replied to a
9.
by dakshgupta 8mo ago
2. There is plenty of evidence for this elsewhere on the site, and we do encourage people to try it because like with a lot of AI tools, YMMV. You're totally right that PR reviews go a lot farther than catching issues and enforcing sta
10.
by dakshgupta 8mo ago
> Independence It is, but when a model/harness/tools/system prompts are the same/similar in the generator and reviewer fail in similar ways. Question: Would you trust a Cursor review of Claude-written code more, less,
11.
There is an AI code review bubble(greptile.com)
351 points by dakshgupta 8mo ago|249 comments
12.
Every GitHub object has two IDs(greptile.com)
327 points by dakshgupta 8mo ago|75 comments
13.
by dakshgupta 9mo ago
We have ways to approximate our impact on code quality, because we track: - Change in number of revisions made between open and merge before vs. after greptile - Percentage of greptile's PR comments that cause the developer to change t
14.
by dakshgupta 9mo ago
Apologies, that is poor wording on our part. It's internal data from engineers that use Greptile, which are tens of thousands of people from a variety of industries. As opposed to external, public data, which is where some of the chart
15.
by dakshgupta 9mo ago
Most of our customers are enterprises, so I feel relatively comfortable assuming they have some decent testing and QA in place. Perhaps I am too optimistic?
16.
by dakshgupta 9mo ago
Thanks! The first 4 charts as well as Chart 2.3 are all from our data!
17.
by dakshgupta 9mo ago
This is a good one, wish we had included it. I'd run some analysis on this a while ago and it was pretty interesting. An interesting subtrend is that Devin and other full async agents write the highest proportion of code at the largest
18.
by dakshgupta 9mo ago
How would you measure code quality? Would persistence be a good measure?
19.
by dakshgupta 9mo ago
This is a great suggestion. I'll note it down for next years. Curious, do you think this would be a good proxy for code quality?
20.
by dakshgupta 9mo ago
This is per month, I see now that's not super clear on the chart!
21.
by dakshgupta 9mo ago
We're careful not to draw any conclusions from LoC. The fact is LoCs are higher, which by itself is interesting. This could be a good or bad thing depending on code quality, which itself varied wildly person-to-person and agent-to-agen
22.
by dakshgupta 9mo ago
We weren’t able to find a good quality measure. LLM-as-judge dint feel right. You’re correct that without that the data is interesting but not particular insightful.
23.
by dakshgupta 9mo ago
We weren’t able to agree on a good way to measure this. Curious - what’s your opinion on code churn as a metric? If code simply persists over some number of months, is that indication it’s good quality code?
24.
by dakshgupta 9mo ago
We expressly did not conclude that more lines = better. You could easily argue more lines = worse. All we wanted to show is that there are more lines.
25.
by dakshgupta 9mo ago
We were trying not to insinuate that, because we don’t have a good way to measure quality, without which velocity is useless.
26.
The State of AI Coding Report 2025(greptile.com)
132 points by dakshgupta 9mo ago|112 comments
27.
by dakshgupta 9mo ago
Hi, I'm Daksh, a co-founder of Greptile. We're an AI code review agent used by 2,000 companies from startups like PostHog, Brex, and Partiful, to F500s and F10s. About a billion lines of code go through Greptile every month, and w
28.
by dakshgupta 10mo ago
Greptile | Software Engineer (junior, senior, staff)| San Francisco ONSITE | https://greptile.com Greptile is building AI agents that catch bugs in pull requests. Over 2,000 teams including Brex, Whoop, and Substack use Greptile
29.
The secret channel that carried 40 years of text messages(greptile.com)
5 points by dakshgupta 10mo ago|0 comments
30.
by dakshgupta 11mo ago
Greptile | Software Engineer | ONSITE San Francisco (SF) | https://greptile.com Greptile is working on AI agents that catch bugs and enforce standards in pull requests. Reviewing nearly 1B lines of code a month for 1000+ compani

More ›