MarkyPc3

A few suggestions: - attend meetups, but not just one. Create a longer term relationship with those you would consider for this role. The likelihood of meeting the co-founder who completes the successful startup formula at a meetup is quite low. You're more likely to find this person in your existing network since that co-founder will also need to be capable of surviving the harsh peaks and valleys of the startup's lifecycle, together with you. Weak relationships are harder to maintain throughout this journey. There are, of course, exceptions. - Evaluate tools that would allow you to build your product yourself. You'll be surprised at how far you can go with the tools available to non-technical founders. - Consider hiring someone. A strong hire would create a working relationship and may end up being the best fit for the co-founder role. You might even get by with this as the long term arrangement. - Be charismatic and open minded. You've probably already met your future co-founder.

Don't let it slow you down. Think about things practically. If you didn't get accepted now, that only means you won't receive money from them for now. You can still always get in touch and ask questions and hopefully get answers. The most important part of YC is that you have an intense drive to get work done without being distracted. You have a [petrifying] sense of accountability and a demo day to get ready for. If you can set these up for yourself, then it could be just as good. The only thing missing would be to get in touch with partners who'd otherwise have more time to speak with you and meet you in person. Email your questions. You may get answers and you may even build meaningful relationships eventually.

Last I applied as a single founder I got an interview. Now I have a cofounder and made significant progress but our application didn't earn us an interview (the second time applying with this idea.) Perhaps I took something for granted when i applied this time so the app turned out weaker or disappointing but I realize how lucky I was to get feedback last time as opposed to none at all now.

Sorry for assuming C++ or C#

If the beginner understands functions I tell them it's the specific object running the function call. If not, I tell them it's the object that owns the most immediate scope (as in the one "running the code"). Also important here is the definition of what an object is. The key sentence to memorize is: "An object is an instance of a class" which is to say that the two are not the same. Saying a class is a blueprint and an object is the actual house that was built according to the blueprint (the class definition)is a good way to get this through. "This" in the above analogy more easily means a reference to a specific house.

Probably because of the inferiority complex the infinity characteristic imposes on you. Makes you feel inadequate for not completing something. It's ironic as it had already existed in a sense - with TV. It never ends either and powerfully attracts people to continue watching.