> But I can't run it without the other founder, there's too much work. Is it really too much work? Have you tried to do all the work yourself? I bet you'll f

> But I can't run it without the other founder, there's too much work. Is it really too much work? Have you tried to do all the work yourself? I bet you'll figure out a way to get it done with or without the other founder (if you're passionate enough). Maybe it's a matter of cutting out features, but maybe those features weren't so important to begin with. Constraints drive innovation. I say go for it. Worst case scenario - it doesn't work, you call it quits, you snag the valley job. If it makes you feel any better, I'm graduating in December (enterprise systems engineering), and I'm in a similar situation. I tossed around the idea of working on my own projects vs getting a "real" job. To make my choice easier, I applied to and interviewed at exactly zero companies. I decided to take 6-9 months to see what I can do. I told myself it's now or never. To make things more interesting, I will certainly be broke by January, I have no investors, and I barely have an MVP. Also, I just started learning how to program within the past few months, and I am a single founder. Talk about constraints! =]