baristaGeek

9 ms·

61.
by baristaGeek 3y ago
Great product! I really liked the UI/UX, and the fact that you provide an example is awesome. I played around with it for about 10 minutes, but one thing wasn't entirely clear to me: How do I import my API if it's not an NPM
62.
Reimagining code review with RAG to save us from LGTM(watermelontools.com)
2 points by baristaGeek 3y ago|0 comments
63.
by baristaGeek 3y ago
Works like a charm! Ty
64.
Embracing a Breaking Change as an Innovation Catalyst(watermelontools.com)
2 points by baristaGeek 3y ago|0 comments
65.
by baristaGeek 3y ago
It's important to note that our choice of the watermelon symbol was made two years ago, with no intention of causing discomfort or insensitivity to any situation. We apologize if it has inadvertently caused any unease.
66.
by baristaGeek 3y ago
Thanks for your input! It's a valid concern and something we can improve.
67.
by baristaGeek 3y ago
Thanks for highlighting this for the community! Besides this, you can also see on our repository that we only send line diffs, titles of pull requests, and descriptions of pull requests to the GPT API, not your entire codebase.
68.
by baristaGeek 3y ago
We strongly believe in opening up the codebase to embrace transparency and show users that their code is being read, not stored. That being said, we understand that many companies can't use OpenAI-powered products because of the lack o
69.
by baristaGeek 3y ago
It's valid that you bring this up! We're still discussing this. We do have a plan to open what's currently built entirely, and later build proprietary features inside an /ee dir. You can read more about our strategy on o
70.
by baristaGeek 3y ago
There's absolutely nothing "ballsy" about describing our product as a "copilot" as a lot of other people are doing, or about choosing to host it on GitHub – the go-to platform for open source repositories. Our produ
71.
by baristaGeek 3y ago
I hadn't heard about them before. Their product looks awesome! From checking out their website, it seems like they've developed a more advanced way of chatting with line diffs, whereas we've built a superior PR summary system
72.
by baristaGeek 3y ago
We appreciate your curiosity about our app. Just to clarify, we're actually a RAG application, not a wrapper. Our focus is on reviewing PRs in a manner similar to human reviewers, by tracing code context from various sources. Currently
73.
by baristaGeek 3y ago
Currently, we're running an experiment where we provide teams with 500 free PR analyses each month. Beyond that, we charge $16 per month for each seat.
74.
by baristaGeek 3y ago
We should definitely do that. Thanks for your input!
75.
by baristaGeek 3y ago
Thank you so much for your support! We truly appreciate it.
76.
by baristaGeek 3y ago
Hello, the other Esteban (CEO) here. I'll also be available to answer any questions from the community and to receive your feedback.
77.
by baristaGeek 3y ago
Huge fan of SemanticDiff! We still see this technology being able to handle edge cases (as you mention) such as certain movements of blocks of code to another file.
78.
by baristaGeek 3y ago
In a world where you can pass a whole git repo as part of the context window of a model, wee see potential not only to reduce hallucination but on diffing based on a company's code style
79.
Will LLMs Eclipse the Classic Code Diff Algorithms?(watermelontools.com)
2 points by baristaGeek 3y ago|4 comments
80.
by baristaGeek 3y ago
It really comes down to personal preference rather than the trends in the job market when comparing those two in-demand skills. Personally, I'm more drawn to "applied AI engineering" – it's like a blend between data scie
81.
by baristaGeek 3y ago
Hey there! Co-founder of Watermelon here. Watermelon is your open-source copilot for code reviews. Our GitHub app dives into PRs, providing context using information pulled from platforms like GitHub, Slack, Linear, and Confluence, to name
82.
by baristaGeek 3y ago
Replit to build very quick prototypes of some script and see what it would console log. GitHub Codespaces for quick stuff, I prefer my IDE.
83.
How to add web-tree-sitter to a NextJS project?(stackoverflow.com)
1 points by baristaGeek 3y ago|0 comments
84.
by baristaGeek 3y ago
We completely agree with this! It's better to say, "It's imperfect due to X reason, but let's merge and fix it later," rather than just a "lgtm" message that doesn't educate anyone."
85.
by baristaGeek 3y ago
What we argue is that code review's goal is not only preventing the deployment of bad code to production (very important by itself) but also osmote information about the codebase to everyone on the team.
86.
Just LGTM on Pull Request comments? You're failing as a dev(watermelontools.com)
4 points by baristaGeek 3y ago|7 comments
87.
The GitHub for Code Review UI Needs Serious Innovation(watermelontools.com)
4 points by baristaGeek 3y ago|3 comments
88.
How to ruin your life trying to do gitflow(watermelontools.com)
1 points by baristaGeek 3y ago|0 comments
89.
by baristaGeek 3y ago
Keep it going! Our startup's extension is listed on Open VSX Registry and we're very happy doing so.
90.
Show HN: Watermelon – Source-available passive documentation search engine(github.com)
3 points by baristaGeek 3y ago|0 comments

More ›