Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

If you're a programmer, and you're relatively young (like under 40) you probably don't have a lot of experience. Sure you have a lot of experience programming, and solving problems. But it's VERY unlikely that you know an industry, and it's unsolved or badly solved problems. To get to know these problems, I think you need some outsider experience.

For example, i'm in the healthcare industry. I can name a whole bunch of problems here, but none of them are ripe for a new startup. That's because I really only find out about a problem from my little part of the world. The few times i've had glimpses beyond my world I certainly haven't had enough of a glimpse to really try and tackle it.

So to me, that's important. Without a cofounder who really knows an industry, you're going to work on 1st world problems that a normal person might run into, that are solvable by a single person.

To be honest, of the problems left in that space they're not really interesting businesses. Either they won't make too much money, or they solve a boring non-problem.

As a technical person I want to find someone who has ran into good problems, and will know if a solution will work or not.



You're making a couple assumptions I disagree with. Even when I was under 40 I knew of more problems that needed to be solved than I could possibly address. Every job I've had has exposed me to industry problems that were big... and you can found a company in an industry, be a single founder and then hire people who have domain expertise. Domain expertise doesn't mean one has to be a cofounder.

Also, consider does this domain expert have the background in startups that would be useful? Or were they being an employee in that domain?

I can think of a half dozen purely technical problems that would improve a billion people's lives-- and I'm talking purely software here.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: