I've been following this project for so long, super cool to see you guys here!
Ty! Always looking to learn about new ways to add value to you
Show HN: Watermelon – open-source VSC ext. to document code and view Git blame
31–40 of 43 posts
Re: Show HN: Watermelon – open-source VSC ext. to document code and view Git blame
#32nicorojas9, alan_arguello, jgarzonebrath and oarojas were all accounts which are between 2 year and 90 day old without any comments. Suddenly they decided to comment for the first time on this specific submission. And all within one hour. And all to basically write the same thing. The Watermelon authors are lucky or maybe it is Friday the 13th.
Always happy to verify my identity Loic.
I saw that Watermelon was on HN and I did made a first comment, because I have been following the project and I like to support other founders who happen to be my friends.
And indeed, they are "lucky" to have people that like the team and project. Hope that it is the same case with you and people that you know :).
Re: Show HN: Watermelon – open-source VSC ext. to document code and view Git blame
#33Hey Esteban, it’s Sebastian. Huge congrats on your HackerNews launch!!! I had the pleasure of working with Esteban (aka baristaGeek) at Cerebrum. Great guy. There’s a saying that the best employees go on to be founders, and I can definitely see that in what Watermelon is becoming. Very exciting! And yes! The code onboarding problem is always there. Watermelon providing that historical context is huge. P.S. I just hap…
Haha!
"The other Esteban" here.
Thanks for the comment, we've been hard at work.
Hope to see you again soon!
Re: Show HN: Watermelon – open-source VSC ext. to document code and view Git blame
#34Love this! If you can pull in info from Slack/Discord convos that would be a big unlock. Do you plan to make this available to private repos shortly? Would love to try it out on an internal one, as we always find ourselves repeating information when onboarding new team members.
Re: Show HN: Watermelon – open-source VSC ext. to document code and view Git blame
#35nicorojas9, alan_arguello, jgarzonebrath and oarojas were all accounts which are between 2 year and 90 day old without any comments. Suddenly they decided to comment for the first time on this specific submission. And all within one hour. And all to basically write the same thing. The Watermelon authors are lucky or maybe it is Friday the 13th.
Always happy to verify my identity Loic. I saw that Watermelon was on HN and I did made a first comment, because I have been following the project and I like to support other founders who happen to be my friends. And indeed, they are "lucky" to have people that like the team and project. Hope that it is the same case with you and people that you know :).
Then, as a good friend, take the time to provide a comment with more insights. We will all benefit from them. I looked at the comments because the website has not a lot of information and I was expecting to learn more from the comments.
Note: This is the first time I looked at the origins of comments in a submission because they really looked like fake comments and this annoyed me terribly as I want HN to stay free of them.
Re: Show HN: Watermelon – open-source VSC ext. to document code and view Git blame
#36I wonder what are the future plans and features of Watermelon? Currently it feels like it does not bring a lot, or any, new things to VS Code ecosystem.
- GitLens is the extension every Git user should have installed, and it for example automatically gives you the git blame on every line
Then depending a bit on the version control system & language used, there are "native" extension for PR and documentation.
- Github pull requests & issues integrates nicely with the GitLens blame - hover the blame and you'll see the PR. Also has bunch of PR & Issues related functionalities
- autoDocstring (Python) for generating documentation "automatically" inside the code, where it belongs IMHO.
Re: Show HN: Watermelon – open-source VSC ext. to document code and view Git blame
#37Love this! If you can pull in info from Slack/Discord convos that would be a big unlock. Do you plan to make this available to private repos shortly? Would love to try it out on an internal one, as we always find ourselves repeating information when onboarding new team members.
Hi there and Ty!
1. We are already available for private repos. If you authenticate you’ll be able to use us on any GH private repo
2. Yes! We’re exploring integrating Notion, Jira, and Slack. Stay tuned!
Re: Show HN: Watermelon – open-source VSC ext. to document code and view Git blame
#38I wonder what are the future plans and features of Watermelon? Currently it feels like it does not bring a lot, or any, new things to VS Code ecosystem. - GitLens is the extension every Git user should have installed, and it for example automatically gives you the git blame on every line Then depending a bit on the version control system & language used, there are "native" extension for PR and documentation. - Github…
Hi and Ty for your comment. This is exactly the kinds of questions that we wanna see here because we learn new things with such.
1. GitLens is useful but it only gives you the author of a line, and the commit message. We can do way better than that as we keep indexing info from more sources + organize it in different ways
2. Similar as number 1. We will index info from more sources and organize it better.
3. Didn’t know about autoDocstring but it looks like a great analogous tool to JSDoc. We’ve used JS Doc and think it’s great for documenting functions. However, we believe there is an opportunity for documenting greater level stuff such as the architecture and the relations between modules.
Re: Show HN: Watermelon – open-source VSC ext. to document code and view Git blame
#39Earlier quoted context omitted.
Always happy to verify my identity Loic. I saw that Watermelon was on HN and I did made a first comment, because I have been following the project and I like to support other founders who happen to be my friends. And indeed, they are "lucky" to have people that like the team and project. Hope that it is the same case with you and people that you know :).
Then, as a good friend, take the time to provide a comment with more insights. We will all benefit from them. I looked at the comments because the website has not a lot of information and I was expecting to learn more from the comments. Note: This is the first time I looked at the origins of comments in a submission because they really looked like fake comments and this annoyed me terribly as I want HN to stay free o…
That's true thanks. I'm a heavy user/consumer of YC content, SUS and events, but not of HN. Indeed it would have been more useful for both the community and the team to provide an insightful comment.
Anyways, hope you get the opportunity to try Watermelon and give them an unbiased opinion (as I probably would do), which will help them :)
Re: Show HN: Watermelon – open-source VSC ext. to document code and view Git blame
#40I wonder what are the future plans and features of Watermelon? Currently it feels like it does not bring a lot, or any, new things to VS Code ecosystem. - GitLens is the extension every Git user should have installed, and it for example automatically gives you the git blame on every line Then depending a bit on the version control system & language used, there are "native" extension for PR and documentation. - Github…
Hi and Ty for your comment. This is exactly the kinds of questions that we wanna see here because we learn new things with such. 1. GitLens is useful but it only gives you the author of a line, and the commit message. We can do way better than that as we keep indexing info from more sources + organize it in different ways 2. Similar as number 1. We will index info from more sources and organize it better. 3. Didn’t k…
Sounds good, keep up the good work!