I will say this as a coder who has worked with non-technical founders: unless you bring something to the table other than your idea, good coder's will steer clear.
The amount of work it takes to bring a coding project to fruition is massive. 50+ hour work-weeks, lots of uncertainty and wasted attempts, and a ton of stress from juggling a million moving parts. All while the non-technical dude rests on his laurels and "PM"s his way through the workweek, providing general guidance in pointless meetings. This has been my experience twice and I will never work with a non-technical person again unless A) His idea is entirely groundbreaking and the chance of success is high B) He has strong marketing chops and takes care of the growth question.
Comments
I will say this as a coder who has worked with non-technical founders: unless you bring something to the table other than your idea, good coder's will steer clear.
The amount of work it takes to bring a coding project to fruition is massive. 50+ hour work-weeks, lots of uncertainty and wasted attempts, and a ton of stress from juggling a million moving parts. All while the non-technical dude rests on his laurels and "PM"s his way through the workweek, providing general guidance in pointless meetings. This has been my experience twice and I will never work with a non-technical person again unless A) His idea is entirely groundbreaking and the chance of success is high B) He has strong marketing chops and takes care of the growth question.
You are right and I agree 100%. This is my experience as well.