Hacker News Re-Imagined

Show HN: Watermelon – open-source VSC ext. to document code and view Git blame

Hey there HN! We're a pair of devs looking to get feedback for our open-source project.

We're remote engineers who have contracted for many clients overseas. There's a problem that all codebases share: Onboarding devs to a new codebase is hard no matter what.

We're also open-source engineers and learned about the techniques used in OSS to tackle the problem. Please give us your feedback.

Homepage: https://watermelon.tools/

Repo: https://github.com/watermelontools/wm-extension

Install: https://marketplace.visualstudio.com/items?itemName=Watermel...

  • 61 points
  • 5 hours ago

  • @baristaGeek
  • Created a post

Show HN: Watermelon – open-source VSC ext. to document code and view Git blame


@Loic 1 hour

Replying to @baristaGeek 🎙

nicorojas9, 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.

Reply


@sebmellen 1 hour

Replying to @baristaGeek 🎙

Hey 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 happened to find this at the bottom of the homepage. I had no idea Esteban would be posting here, I just browse HN a lot.

Reply


@nicorojas9 2 hours

Replying to @baristaGeek 🎙

Hey, congrats on the open source approach! I do have a question on your strategy though. How do you get valuable feedback from users? What incentive does your users have in order to communicate with you back and forth trying to build a better product?

Reply


@alan_arguello 3 hours

Replying to @baristaGeek 🎙

Amazing concept! I have been following the process and I'm really excited to see what you guys accomplish. Congrats!

Reply


@a-dub 1 hour

Replying to @baristaGeek 🎙

super 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.

Reply


@igomeza 2 hours

Replying to @baristaGeek 🎙

Used it some weeks ago to understand a package in the kubernetes codebase. Its great for getting insights on an unfamiliar project

Reply


@revenga99 1 hour

Replying to @baristaGeek 🎙

Curious why it is named watermelon.

Reply


@miguelmichelson 1 hour

Replying to @baristaGeek 🎙

I'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!

Reply


@oarojas 3 hours

Replying to @baristaGeek 🎙

Love the open-source approach. Congrats! Great product

Reply


@estebandalelr 5 hours

Replying to @baristaGeek 🎙

Hey! Esteban, the CTO of watermelon here. Feel free to ask any questions, open to answering them :)

Reply


@jgarzonebrath 4 hours

Replying to @baristaGeek 🎙

This concept is very cool. Interesting approach to visualize git blame and the team behind looks outstanding. Congrats guys, downloaded.

Reply


About Us

site design / logo © 2022 Box Piper