Oh man - i've been watching you guys for awhile. We're YC too and building a superapp for sales ppl. Any killer use cases you've seen or imagined for sales (outside of prospecting vid customization?
Just Weta FX - those were the guys and gals that used Weta tooling for producing films and such. Not Weta Tools - those are the guys and gals building and maintaining the Weta tools
Very cool. We're working on something similar but we went more narrow because its really hard to unravel the business context from just the data alone. Ours is ponyrun.ai if you want to check it out. Also open to chat and share learnings if you're open to it.
Ive seen data sets like this and they've been bad. My main issues have been that dataset isn't kept updated, theres no sense of proportion (e.g. is 1% of the team java or 50%), and there's often not enough companies in the dataset.
So bad that I probably wouldn't buy this data without some proof that its good data
Lots of folks are asking "who is this for?". I think that's because the people that should use this don't know that they should yet. And it's probably missing the hotel/car angle too.
This would let people like planners (e.g. destination wedding), events (e.g. festivals), and the like simplify and make money through the entire customer experience/journey.
Congrats on the launch. YC W22 founder who loves gaming and used to work in the gaming industry here. Love the concept and I'm excited to see how you guys grow
If you didn't put it on LinkedIn, the spam callers got it through different ways (sales tooling, direct from data providers, leaks, etc.) If you're putting your phone number out anywhere (even in the signature of your email), they're collecting that info and selling it
Yeah - we've (usenimbus.com - a company in this space) have heard the same about Jetbrains IDEs. You should check out our extension (or others') because there's been a lot of work put into making performance better.
M1s are a mixed bag for this way of working. Pre-M1, devs were running into local computing power issues. Post-M1, more compatibility and stability issues.
Thats definitely one way to do it. Im a founder at a remote dev infra startup (usenimbus.com) and this was the model we started with because it was just so simple. But we quickly learned theres no one size fit all solution so expanded into supporting containers, terraform, etc.
I dont believe this. Went through YC this year and many of the founders had great alternatives. You could say that none of the alternatives were as attractive... but thats how all decisions are made
Extremely biased here. I'm one of the founders of Nimbus (www.usenimbus.com) and we help companies move to cloud dev environments.
Cloud dev environments are a tool like any other. How they're designed matters. A lot of home grown tooling ends up being limited for ease of build out and maintenance cost/effort.
We've made a lot of the opposite decisions and often wonder if we went the right way. Still don't know if it's the right decision but at least our thinking wasn't wrong - so thats a win :)
I cofounded a company and had my first kid 4 months later - it was brutal. I took 2 weeks off completely but then had to take a bunch of days after because babies are hard work.
What I would do next time:
- Take more than 2 weeks (lol)
- Communicate expectations before and during
- Assign out your core responsibilities (start by looking at last months meetings and seeing who wouldve been best to replace you)
- Be available via Slack and E-mail when needed
- Put wife and baby first (this means slack/emails only get tended to when baby is napping and your not cooking/cleaning, etc.)
I think more people on remote environments does lead to better overall experience. But the incremental benefit for each additional team member drops until everyone is working on the cloud - because then you can do some cool things or stop doing some dull things.
That said, we avoid doing anything that forces an entire team to move to our cloud environments. That's an easy way to piss people off and build a crappy product. Hopefully this approach doesnt burn us.