There are at least a couple points in your message that I wanna address.
> genuine insight is very rare and extremely hard to identify.
Insights capable of spawning billion-dollar companies are hard to come-by, indeed! But the smaller the scope of the idea - the bigger number of insights in existence that you can work on. When you can have a PMF on an idea with TAM of $100M in a matter of days, and you don't need VC money to make it happen, AND you can test it out with a rep of the target audience - isn't that something worth pursuing?
> How do you prevent Vibed from becoming a graveyard of half-baked ideas, I mean projects that are trivial, already solved, or fundamentally flawed?
I think people would genuinely not be incentivised to be posting projects for already solved problems, UNLESS the solutions are not exactly accessible to them, which in turn makes those project potentially a good idea still. We are just starting out so I'm not going to pretend I know rn how we would solve every problem we hit along the way (yet I hope we hit many and for a long time, haha), but one of the best ways for us to get the CONTENT we want - would be to work on getting the PEOPLE we need on the platform. We are also pretty well-versed with AI too, so we will be able to do a great moderation too (including a check for past projects that are similar -> thus to discourage repetition and plagiarism).
Thanks for the reply. We are not keeping continuous presence in the country, just have a teammate who lives in Canada, but is from China and would like to visit family for a month or so.
Does anyone know if Amazon Workspace hosted in Tokyo, could be accessed from China? Latency to AWS Japan would likely be one-of/or the lowest from China to an AWS datacenter?
That was my thought as well - basically, how do you know if the strain doesn't kill if you don't check for severe and lethal cases linked to the same strain? I understand the part about looking for specific mutations, and assuming they would indicate the "usual" complications with the deadlier strains would not be present, but mutations are not exactly predictable, right? If they don't cause the sympthoms of the current deadly strain - they may be causing something else completely, which could be as deadly a little bit later down the line - isn't this a reasonble concern, @danieltillett?
Sounds like an unpolished async change - it changes only after the server has confirmed successfully saving. I often hit this in my projects and if I want to be safe I would usually add a progress to make sure the user knows what's happening, but when it's not a critical change (losing a new name of a column would classify for that in my book) I would just apply the new state on the client for better UX, risking losing the change if the user somehow navigates away/kill the app before a request is sent/completed. It's just better UX, IMO.
The status of my application on https://apply.ycombinator.com/ changed and I haven't received an email.
You should check that out.
I wasn't selected for an interview, but I honestly am not too bothered with this. Just woke up from an amazing 8h sleep and even though I have worked every single day for the last 130+, I feel great! I used to be very emotional about rejection (just YC has turned me down 2 times before), but then I was considering every attempt as potentially THE one opportunity I have. Once I realized this is what I am going to do for the rest of my life (building startups) - the anxiety is almost gone.
No matter if my current product fails or not - I'm already a good builder, I'll get better at picking ideas, I'll get even better at telling my story and I'll apply for S19, W20, S20, W21, S21... and however many times I need to until I become a part of this amazing network of people (or until I manage to get a similar level of quality of connections on my own) and so should you, if you are serious about being an entrepreneur.
Why continue to apply without simply building a company instead? Looks like you have the #1 requirement down: tenacity, now you could channel it towards something immediately productive instead of continuing to play the lottery until you win. Note that with your actual company you could still apply to YC.
What made you think that I am not building a company/product? :)
As I said, I am moving forward and will continue applying for every batch of YC, no matter what I am working on (whether it's the same product or something new).
Sounds like you consider YC to be valuable only for idea-stage projects, but that's not true. There are companies that have raised money and still go through YC.
P.S. Viewing your application at YC as "lottery" would likely not get you even an interview. It's not a lottery. My application wasn't strong-enough and that is why it didn't get picked.
There are at least a couple points in your message that I wanna address.
> genuine insight is very rare and extremely hard to identify.
Insights capable of spawning billion-dollar companies are hard to come-by, indeed! But the smaller the scope of the idea - the bigger number of insights in existence that you can work on. When you can have a PMF on an idea with TAM of $100M in a matter of days, and you don't need VC money to make it happen, AND you can test it out with a rep of the target audience - isn't that something worth pursuing?
> How do you prevent Vibed from becoming a graveyard of half-baked ideas, I mean projects that are trivial, already solved, or fundamentally flawed?
I think people would genuinely not be incentivised to be posting projects for already solved problems, UNLESS the solutions are not exactly accessible to them, which in turn makes those project potentially a good idea still. We are just starting out so I'm not going to pretend I know rn how we would solve every problem we hit along the way (yet I hope we hit many and for a long time, haha), but one of the best ways for us to get the CONTENT we want - would be to work on getting the PEOPLE we need on the platform. We are also pretty well-versed with AI too, so we will be able to do a great moderation too (including a check for past projects that are similar -> thus to discourage repetition and plagiarism).
Hope that answers your question(s).