Hey! Esteban, the CTO of watermelon here. Feel free to ask any questions, open to answering them :)
Show HN: Watermelon – open-source VSC ext. to document code and view Git blame
21–30 of 43 posts
Re: Show HN: Watermelon – open-source VSC ext. to document code and view Git blame
#22super cool! have long been interested in tooling for making code archaeology easier! any plans for building extensions for various issue/work tracking systems, wikis, email archives, etc? i've longed for comprehensive views across tickets, pull requests, bug reports and wikis for all relevant knowledge for a given effort in past.
Re: Show HN: Watermelon – open-source VSC ext. to document code and view Git blame
#23Re: Show HN: Watermelon – open-source VSC ext. to document code and view Git blame
#24I've been following Esteban's project recently, I like the product very much it's really handy to give context on what we do on daily basis (coding in my case :D). Build in the open is the way to go, best of lucks to the watermelon team!
Re: Show HN: Watermelon – open-source VSC ext. to document code and view Git blame
#25Hey 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…
Hope we're adding value with our historical context tool. Always glad to listen to your feedback.
Re: Show HN: Watermelon – open-source VSC ext. to document code and view Git blame
#26super cool! have long been interested in tooling for making code archaeology easier! any plans for building extensions for various issue/work tracking systems, wikis, email archives, etc? i've longed for comprehensive views across tickets, pull requests, bug reports and wikis for all relevant knowledge for a given effort in past.
What's your opinion about the create docs direction we're exploring to complement your Indiana Jones coding? (Love your "code archeology" term).
Re: Show HN: Watermelon – open-source VSC ext. to document code and view Git blame
#27nicorojas9, 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.
Wow this Sherlock Holmes-level research. Our close friends did notice we launched. Lol.
It isn't very hard to click on the usernames after you see some suspicious messaging from similar accounts.
Re: Show HN: Watermelon – open-source VSC ext. to document code and view Git blame
#28Re: Show HN: Watermelon – open-source VSC ext. to document code and view Git blame
#29super cool! have long been interested in tooling for making code archaeology easier! any plans for building extensions for various issue/work tracking systems, wikis, email archives, etc? i've longed for comprehensive views across tickets, pull requests, bug reports and wikis for all relevant knowledge for a given effort in past.
Yes! We're exploring Jira, and Notion integrations mostly. We're discarding Slack for the moment because of the technical feasibility, but would be something we look further down the road. What's your opinion about the create docs direction we're exploring to complement your Indiana Jones coding? (Love your "code archeology" term).
i'm more interested in tooling that gives as much context as possible for why something is the way it is. code ages like a novel would as passed through the telephone game. the more context that is readily available for each generation of changes, the more consistent the design remains in the long run.
also, it's incredibly handy when in emergency breakfix situations.
Re: Show HN: Watermelon – open-source VSC ext. to document code and view Git blame
#30Earlier quoted context omitted.
Yes! We're exploring Jira, and Notion integrations mostly. We're discarding Slack for the moment because of the technical feasibility, but would be something we look further down the road. What's your opinion about the create docs direction we're exploring to complement your Indiana Jones coding? (Love your "code archeology" term).
that is less interesting to me personally as that's often handled locally. (most sites with many projects will have some sort of locally customized project boilerplate or template to start with). i'm more interested in tooling that gives as much context as possible for why something is the way it is. code ages like a novel would as passed through the telephone game. the more context that is readily available for each…