From 6/17/2014, 3:33:40 AM till now, @baristaGeek has achieved 747 Karma Points with the contribution count of 343.
Recent @baristaGeek Activity
Very interesting approach! Trying this out right now. A lot of information gets lots with Typeforms, and this could be the disruption of this.
Let me also ask you, do you see yourself competing with Zoom recordings? Would the asynchronous approach be a value prop you would be doubling on?
Granular Access Control
1 points • 0 comments
Please let us know if anything changes on your side!
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.
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!
Ty! Always looking to learn about new ways to add value to you
Ty very much! We'll keep this in mind.
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).
Ty Sebastian! Yeah, Cerebrum was an awesome school.
Hope we're adding value with our historical context tool. Always glad to listen to your feedback.
Ty! Yeah we're an open company (open source, open roadmap, open salaries) and it has worked great.
Wow this Sherlock Holmes-level research.
Our close friends did notice we launched. Lol.
It's the happiest fruit and has emoji :)
Thanks! If you have any suggestions for us please open up an issue on our repo.
Ty! Open source is a very important part of our philosophy.
1. We track which GitHub usernames and repos that use Watermelon, it's the only thing we track. This allows us to go to people and ask them for more detailed feedback. We also get feedback from stargazers and forkers. Because we're open source, people also leave GH issues.
2. The incentive is something very basic: They wanna see a better version of this out there in the world.
Ty Alan! It's great to be surrounded by smart technical people like you.
Ty! This has been an important pillar for us since day 1. We believe a lot in the open source ethos, its transparency, and its collaborativeness.
Ty very much! We're glad we're adding value.
Show HN: Watermelon – open-source VSC ext. to document code and view Git blame
84 points • 42 comments
Thank you for building this for the frontend.
Code Quality Analysis with SonarQube
1 points • 0 comments
site design / logo © 2022 Box Piper