akshaysg

7 ms·

1.
by akshaysg 4mo ago
If you see my reply, I would absolutely love it if you could email akshaysg@haystackeditor.com with some details about your desired use cases!
2.
by akshaysg 4mo ago
Thank you for the kind words! RE Pricing: Because of the high volume of our customers, this is quite necessary unfortunately. We can definitely shift down costs as existing intelligence becomes cheaper though.
3.
by akshaysg 4mo ago
I think that AI coding is only going to grow in usage. I also think that AI more-or-less writes working code that is faithful to the user's prompt. At the same time, AI does not write code that's easy for humans to review, as it w
4.
by akshaysg 4mo ago
Yeah I agree it's a shame. Unfortunately coding has changed fast and I was not confident that the editor was in the correct direction with AI coding becoming so prevalent. I think there is a lot of value with "reconnecting" w
5.
by akshaysg 4mo ago
I think Haystack offers: 1. A centralized review mechanism for a team or org that operates on coding agent conversations in addition to diffs (and the codebase). It evaluates multiple different variables (e.g. how sensitive are the changes,
6.
Show HN: Haystack – Review the PRs that need human attention(haystackeditor.com)
45 points by akshaysg 4mo ago|17 comments
7.
by akshaysg 6mo ago
I've been thinking a lot about this! Redoing the work as smaller PRs might help with readability, but then you get the opposite problem: it becomes hard to hold all the PRs in your head at once and keep track of the overall purpose of
8.
Show HN: Haystack Review – Have a conversation with your pull request(tryhaystack.dev)
1 points by akshaysg 7mo ago|0 comments
9.
Show HN: Flag AI Slop in PRs(haystackeditor.com)
3 points by akshaysg 8mo ago|0 comments
10.
Show HN: Haystack Slop Detector – a lightweight barrier against unreviewed PRs(haystackeditor.com)
3 points by akshaysg 9mo ago|0 comments
11.
Show HN: I made a Halloween roguelike where you battle to merge a 1000-line PR(haystackeditor.com)
2 points by akshaysg 11mo ago|2 comments
12.
Show HN: Code Review Survivors – a roguelike where you merge a 1000-line PR(haystackeditor.com)
1 points by akshaysg 11mo ago|0 comments
13.
by akshaysg 1y ago
Will add this then!
14.
by akshaysg 1y ago
We use a mixture of LLMs (e.g. to identify the important variables to trace), language servers (to understand where a variable is originally defined and where it's used).
15.
by akshaysg 1y ago
We may go back to code visualization for editors, but after testing it with a lot of engineers, we found that it was too confusing for code reviews. The main issue was just how alien the interface is!
16.
by akshaysg 1y ago
> 1. Allow me to step through the code execution paths that have been modified in the pull request, based on the tests that have been modified. Not sure if I fully grasp this! We tried to kind of do this in previous iterations (show call
17.
by akshaysg 1y ago
Ahah! Thanks for the feedback.
18.
by akshaysg 1y ago
Yes! I personally iterate without understanding the code too much (since it'll change), and fully assess what Claude Code (in my case) has done after I finished a piece of work.
19.
by akshaysg 1y ago
Thanks for the feedback! Not sure if I fully grasp what you mean by dog whistling, but at the end of the day, like another commenter said, Haystack is also pretty helpful for when you're done experimenting with a piece of work and need
20.
by akshaysg 1y ago
Yes! We haven't wholly given up on that idea by the way ;)
21.
by akshaysg 1y ago
>If AI writes all of the code, we will need to max out humans’ ability to do architecture and systems design. Strongly agree with this. There are demos that you're able to try, by the way!
22.
by akshaysg 1y ago
Yeah I did this too as an engineer! I think this is a valid part of the "crafting PR" skill that's under appreciated, and part of the goal of Haystack here is to make that part of PR craft effortless.
23.
by akshaysg 1y ago
Interesting. At my previous company there was a debate about smaller PRs vs bigger PRs and the end conclusion was that there are tradeoffs in being able to deal with 2-5 bite-sized PRs vs one large PR. The largest one being that it's h
24.
by akshaysg 1y ago
Sorry to clarify: you hit "back" after traversing from the summary but it doesn't go back? If so, that's a bug! Or do you mean that doing the browser navigation of "back" should bring you to the summary (initia
25.
by akshaysg 1y ago
> you likely have a bigger organizational issue Could you expound on this? In my experience as a software engineer, a pull request could fall into one of two buckets (assuming it's not trivial): 1. The PR is not organized by the aut
26.
by akshaysg 1y ago
Thanks for the opinion! That makes a lot of sense and I like the concept of being an extension of a user's own analysis vs hosing them with information. Yeah originally I thought of using yellow/brown or yellow/black but for
27.
by akshaysg 1y ago
Trying to fix/find this! Could you email me the repo details? Very sorry for the error here. In terms of auth: you should get an "unauthenticated" if you're looking at a repo without authentication (or a non-existent rep
28.
by akshaysg 1y ago
1. Pricing would be $20 per person and we'd spin up an analysis for every PR you create/are assigned to review 2. We don't train or retain anything related to your codebase. We do send all the diffs to Open AI and/or Ant
29.
by akshaysg 1y ago
There's a GitHub app that you can install on your repo. If you install and subscribe to the product, we create a link for you every time you make a pull request. We're working (literally right now!) on making it create a link ever
30.
by akshaysg 1y ago
That's fair! If there were a "minimal" mode where you could still access callers, data flows, and dependencies with no AI text, would it be helpful for your reviews?

More ›