dakshgupta

10 ms·

91.
by dakshgupta 2y ago
This is a real shortcoming, the engineers that ship feature X will not be responsible for the immediate aftermath. Currently we haven’t seen this hurt in practice, probably because we are very small and in-person, but you might be correct a
92.
by dakshgupta 2y ago
I’m generally a strong believer in “if it’s not measured it’s not managed” so this seems like it would be useful to explore. I suspect it’s tricky to assign a cost to a bug though.
93.
by dakshgupta 2y ago
My theory is that to outsiders software development looks closer to other generic computer based desk jobs than to the job of a writer or physical builder, so to them it’s less obvious that programming needs “flow” too.
94.
by dakshgupta 2y ago
I suspect as the company gets larger time between defensive sprints will get longer, but yes, for smaller teams this is what keeps quality high, you’ll have to clean up your own mess next week.
95.
by dakshgupta 2y ago
This is interesting because it’s what I imagine would happen if we scaled this system to a larger team - offense engineers would get sloppy, defensive engineers would get overwhelmed, even with the rotation cycles. Small, in-person, high-tr
96.
by dakshgupta 2y ago
To add - I personally enjoy defense more because the quick dopamine hits of user requests fix -> fix issue -> tell user -> user is delighted is pretty addictive. Does get old after a few weeks.
97.
by dakshgupta 2y ago
There is certainly some razor applied on whether a request is unique to one user or is widely requested/likely to improve the experience for many users
98.
by dakshgupta 2y ago
This makes me want to delete the post.
99.
by dakshgupta 2y ago
I am surprised and impressed a company at that scale functions like this. We often internally discuss if we can still doing this when we’re 7-8 engineers.
100.
by dakshgupta 2y ago
These assumptions are most likely important and true in our case, we work out of the same room (in fact we also all live together) and 3/4 are equally skilled (I am not as technical)
101.
by dakshgupta 2y ago
A triage queue makes a lot of sense, only downside being the challenge of getting a lot done without interruption.
102.
by dakshgupta 2y ago
Good point, we will usually only rotate when the long running task is done but eventually we’ll arrive at some feature that takes more then a few weeks to build so will need to restructure our methods then.
103.
by dakshgupta 2y ago
All of these are great points. I do want to add we rotate offense and defense every 2-3 weeks, and the act of doing defense which is usually customer facing gives that half of the team a ton of data to base the next move on.
104.
Splitting engineering teams into defense and offense(greptile.com)
212 points by dakshgupta 2y ago|122 comments
105.
AI will not replace human code review(greptile.com)
1 points by dakshgupta 2y ago|0 comments
106.
by dakshgupta 2y ago
So glad you like it - we were worried it was too silly. The logo is supposed to be a reptile claw but we might modify it to make that more obvious.
107.
by dakshgupta 2y ago
I work at Greptile and agree on all three criticisms. 1) is a bug we haven't been able to fix, 2) has to do with the high cost of re-indexing, we will likely start auto-updating the index when LLM costs come down a little, and 3) has t
108.
by dakshgupta 2y ago
Good catch! This is a mistake, fixing now.
109.
by dakshgupta 2y ago
That form is if you want to install the code review bot or other GitHub integrations for free on your repo . If you want to chat with your repo for free you can do that on the website, assuming it’s a small public repo.
110.
by dakshgupta 2y ago
Pushed a fix, thanks
111.
by dakshgupta 2y ago
Just fixed, sorry
112.
by dakshgupta 2y ago
Sorry, just fixed
113.
by dakshgupta 2y ago
Sorry, fixed
114.
by dakshgupta 2y ago
We use tree-sitter right now and experimenting with call graphs currently. Will write about the results when we have data on that.
115.
by dakshgupta 2y ago
Free for small open source repos + 300 large open source repos. Code MISTRAL100 at checkout for a free month of Pro.
116.
Searching a Codebase in English(greptile.com)
56 points by dakshgupta 2y ago|21 comments
117.
Show HN: Q&A any codebase over REST API(docs.greptile.com)
3 points by dakshgupta 2y ago|0 comments
118.
by dakshgupta 2y ago
Curious on why you went with Codestral for autocomplete, does it outperform other local models? How is the performance compared to GPT or Claude for autocomplete? Any plans to finetune Codestral for this specific usecase?
119.
by dakshgupta 2y ago
IMO data scientists often are used to the jupyter form factor instead of the editor form factor, so I see why they would prefer this thing.
120.
Greptile raises $4M to build the AI codebase expert(techcrunch.com)
1 points by dakshgupta 2y ago|0 comments

More ›