gillh

5 ms·

1.
Code is no longer the bottleneck. Understanding is(coderabbit.ai)
2 points by gillh 2mo ago|0 comments
2.
by gillh 8mo ago
We also use proxies with CodeRabbit’s sandboxes. Instead of using tool calls, we’ve been using LLM-generated CLI and curl commands to interact with external services like GitHub and Linear.
3.
Why is GPT-5 a generational leap in reasoning?(coderabbit.ai)
1 points by gillh 1y ago|0 comments
4.
by gillh 2y ago
This topic has been done to death. Too many OSS options in the last ~10 years with very little differentiation. Let's talk LLMs instead.
5.
by gillh 2y ago
Have to provide precise instructions to LLMs to get anything useful. Instructions for operating the "Holy hand grenade of Antioch" from Monty Python and the Holy Grail are a good example: ''First shalt thou take out the
6.
by gillh 3y ago
Combination of zsh completions with fzf picker and gh copilot for CLIs. I have a good setup here that you can learn from - https://github.com/fluxninja/dotfiles
7.
by gillh 3y ago
Anyone interested in load shedding and graceful degradation with request prioritization should check out the Aperture OSS project. https://github.com/fluxninja/aperture
8.
by gillh 3y ago
When people ask us about any other AI tool, our standard reply is - "Please try both tools to see the difference and choose the one you like." We will appreciate the same courtesy from our competitors. Cheers!
9.
by gillh 3y ago
I see that the handful of Ellipsis "buddies" here are upvoting your post. :) CodeRabbit employees wouldn't usually be commenting here to spoil your "moment," but this reply is entirely wrong on so many levels. The f
10.
CodeRabbit – The AI-First Code Reviewer(coderabbit.ai)
1 points by gillh 3y ago|0 comments
11.
Show HN: Rate limiting, caching and request prioritization for AI apps(fluxninja.com)
10 points by gillh 3y ago|0 comments
12.
by gillh 3y ago
Anyone looking to build a practical solution that involves weighted-fair queueing for request prioritization and load shedding should check out - https://github.com/fluxninja/aperture The overload problem is quite comm
13.
by gillh 3y ago
Interesting use-case: We recently started using ast-grep at CodeRabbit[0] to review pull request changes with AI. We use gpt-4 to generate ast-grep patterns to deep-dive and verify pull-request integrity. We just rolled this feature out 3 d
14.
by gillh 3y ago
FluxNinja [0] founder here. I developed an in-house AI-based code review tool [1] that CodeRabbit is now commercializing [2]. I did it because of the increasing frustration due to the time-consuming, manual code review process. We tried sev
15.
Managing OpenAI Rate Limits with Request Prioritization(blog.fluxninja.com)
1 points by gillh 3y ago|0 comments
16.
by gillh 3y ago
I work at FluxNinja CodeRabbit is a customer of ours - https://docs.fluxninja.com/blog/coderabbit-openai-rate-limit...
17.
OpenAI client-side rate limits with request prioritization(blog.fluxninja.com)
2 points by gillh 3y ago|0 comments
18.
by gillh 3y ago
In addition to code generation, our team has found the new AI code review tools to be quite useful as well. We use CodeRabbit and we keep finding issues/improvements in every other PR.
19.
CodeRabbit Manages OpenAI Rate Limits with Request Prioritization(blog.fluxninja.com)
1 points by gillh 3y ago|0 comments
20.
CodeRabbit: Overcoming LLM limitations to review large pull requests(coderabbit.ai)
1 points by gillh 3y ago|0 comments
21.
AI and the Future of Code Reviews: A Deep Dive into CodeRabbit(coderabbit.ai)
2 points by gillh 3y ago|0 comments
22.
Observing Much, Achieving Little – The Reliability Paradox(blog.fluxninja.com)
1 points by gillh 3y ago|0 comments
23.
by gillh 3y ago
We haven’t used functions as our text parsing has been pretty high fidelity so far. It’s because we provide an example of the format that we expect. We didn’t feel like fighting too hard with LLMs to get structured output. You will also not
24.
by gillh 3y ago
We have been doing this at CodeRabbit[0] for incrementally reviewing PRs and allowing conversations in the context of code changes, giving the impression that the bot has much more context than it has. It's one of the few tricks we use
25.
Observing Much, Achieving Little – The Reliability Paradox(blog.fluxninja.com)
2 points by gillh 3y ago|0 comments
26.
Observing Much, Achieving Little – The Reliability Paradox(blog.fluxninja.com)
13 points by gillh 3y ago|0 comments
27.
Rate-Limiting Primer(blog.fluxninja.com)
11 points by gillh 3y ago|0 comments
28.
by gillh 3y ago
Prioritized load shedding works well as a last resort [0]. The idea is simple - - Detect overload/congestion build-up at the database - Apply queueing at the gateway service and schedule requests based on their priority - Shed excess r
29.
by gillh 3y ago
Fascinating historical insight! We have a team of 20 engineers currently working on solving this problem in the context of API requests and service chains. Do you know JMS @ Penn? Asking because he did some work in ATM networks, QoS etc. He
30.
by gillh 3y ago
We built a fair scheduler for APIs and it's in the open source - https://docs.fluxninja.com/concepts/scheduler/load-scheduler I wish more people knew about this project!

More ›