956 karma · joined June 17, 2014
https://twitter.com/helloteban https://github.com/baristaGeek https://www.linkedin.com/in/tebanvargas/
Feel free to ping me! estebanvargas94 [at] gmail [dot] com
[ my public key: https://keybase.io/baristageek; my proof: https://keybase.io/baristageek/sigs/xvrFueBx0GMNM1qPjertwxrGmgyPzGzabPoXl_Q02Io ]
Medellin, Colombia
Do your diligence, and your technical/communication/leadership interviews to make sure you're hiring the right person.
And if it doesn't work out after 2-3 months, fire the person. It happens in all formats of work whether it's remote, hybrid, or onsite.
What's the difference between a foreigner with an accent in your onsite team VS a foreigner that's remote in US timezones (LatAm)? Why just open the job for US-remote?
Compliance? Deel/Remote can help you with that.
Security? It applies if you're working on defense software, but other than that...?
If this is happening in the middle of a VC downturn, imagine how it's going to be once we're back to good times.
On the challenging side: How does this compare to GitHub's Slack bot? It looks like it's just a slight improvement. What's your vision to make this a 10xer?
Very cool overall! It's a good start. We'll try this out.
About the ideal size and security concerns: We've actually seen the most pushback from very small teams (5 or less engineers). I'm not sure why exactly, but my best guess is that as companies grow, it simply becomes more normal for them to give access to these tools and they see that nothing bad happens (they end up getting a lot of value actually).
However, we can't integrate with the self-hosted/enterprise versions of GitHub, VS Code/Slack, etc. yet which is what our potentially best customers in the future use.
Because of that, the ICP is engineering teams sized between 15 and 150
You can't limit which repos in an organization you're gonna give it access to, but you can limit which organizations you are going to give it access to.
Starting with an organization that has public repos is a good way of starting, indeed.
In fact, we wrote this blog post where we talk about how we're building this without storing your code or passing it through our server at all: https://www.watermelontools.com/post/building-a-code-archeol...
You still have to give us read access to your GitHub, Slack, Jira, etc. Which is still asking for access to corporate info, but you know... people are very used to giving access to these tools via oAuth flows.
Regarding running on dev computers, we have one answer to that: Providing value as a GitHub Action. We still haven't launched it (it's gonna happen very soon), but our hypothesis is that by packaging the product in such format, we'll be able to address that very valid concern.
Thanks!
Besides the GitHub (and its counterparts) Action, I can tell you that we have ideas for:
- A Discord integration
- Fine-tune GPT (with Git, Slack and Jira data) to be able to ask questions specific to your codebase
- An expansion to Intelli J
Thanks for your comment. It's something we should be more clear about.
- Go to a file / highlight a block of code you want to understand at depth
- We take the commit hashes for the lines selected (the whole file if no LOC selected)
- We pass those commit hashes as a parameter to the GitHub/GitLab/Bitbucket API to obtain all the associated PRs
- We sort those PRs by relevance (using number of comments as the heuristic)
- With the title of that PR, we search for the Slack threads and Jira tickets most closely associated to that PR title (if you optinally integrated Slack and/or Jira)
- We aggregate to a GPT prompt the title and body of the most relevant piece of info from each source, to finally generate a summary of that code context.
$24/year and you can basically do anything you want.
All you gotta do is select the desired interval, you tell easycron which endpoint you wanna hit, and that's it.
I just completed my onboarding flow your Discord server and it was pretty neat. Quick question about that: Do you ask for the region of the community member with the purpose of understanding where your users are located, or do you use that as a parameter for some configuration of how the Discord server works for that user specifically?
These things get blurry with global markets and jurisdictions, but I would definitely call them an indian company.
I think this makes sense because switching between them can be done very easily, just change the string from `plan:pro:annual@0` to `plan:pro:monthly@0`. As long as I can write some client side code that allows me to change if the end user is getting access to `plan:pro:annual@0` or `plan:pro:monthly@0` based on what they select on a UI.
> It seems possible. How do you envision the Auth0 action behaving with Tier?
Sorry, I'm not familiar with Auth0 actions. It was just an open-ended question because I saw someone proposed this on your Slack group.
With our current architecture (a very simple one) a simple thing such as iterating on the price of our product requires changing an env var on Vercel. Not complicated, but feels cumbersome for changing a price. Iterating this on a pricing.json file feels easier.
Things get more complex if we decide to do something like giving the user the possibility of choosing between a monthly or a yearly subscription (with a variable quantity, because we charge per seat). That would imply a code refactor.
Would tier.run help us with that????
Really excited about feature flags as well. How would this work exactly? Do I set up which features belong to every plan on the pricing.json file, and then consume your SDK on the frontend to only show the tier to a certain category of paying user?
We currently handle that by querying a SQL table of paying users, and if the email address of the authed user belongs to the table, we show the feature, else not.
I also saw you want to build your product as an Auth0 action. Would that be used for this use case?
Anways, congrats on the launch!!
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?