Well there is this strange thing called open source software where I believe people work for free.
Jokes aside, I can understand why this guy has trouble finding a technical cofounder. It's all in his attitude. A partnership needs to be on an equal footing with a large degree of mutual respect. Of course it's hard to tell from just one blogpost, but it might be the problem.
"Well there is this strange thing called open source software where I believe people work for free."
Most of the time those people don't work for free, they just decide to release the code they've made with the goal of getting paid. Basically, open source software is not the goal, just a (generous) side effect.
He even says in his bio: "In addition to recruiting, Michael is active member of San Francisco's open source software community. He organizes events aimed at teaching people about technology, is a teaching assistant for Ruby on Rails courses..."
Mind boggling that he is an active member in the SF open source community and still thinks that developers don't work for free on worthwhile ideas.
Agreed. The other challenge is getting the software engineer to buy into the plan. Even if they're on equal footing, they may not feel like it because they ultimately believe it's viable. It's also harder to feel good about writing software without cash in the customer validation phase. If you have to pivot and walk away from code already written, it's hard to feel good about that.
Well there is this strange thing called open source software where I believe people work for free.
Jokes aside, I can understand why this guy has trouble finding a technical cofounder. It's all in his attitude. A partnership needs to be on an equal footing with a large degree of mutual respect. Of course it's hard to tell from just one blogpost, but it might be the problem.