Hacker News Reader

I don't know how much non-technical work remains. If I knew that, then that would mean that I'm in charge of both technical and non-technical work, with him acting as an employee and not a co-founder. That I can't count on him to "own" his area within the company is precisely the problem.

View on HN

That's not what knowing implies. Why don't you know? You claim to be committed to your idea yet only know half of what is going on and thus only half of what it is going to take to launch?

If you're so keen to get rid of him why do you not already know what he's not doing and needs to do?

How will getting rid of him help you if even you don't know what you need to do to make this work?

There's 2 of you, you don't have and can't afford to have silos yet.

Naive developer indeed

I know some of what he's not doing, because it's things we've been talking about for several months. But of course I don't know every single non-technical requirement. Isn't the point of having a partner to split up the work? If I did all the research into what legal requirements we have within our field, etc. then I'd be doing all of the work, instead of just most of it.

Reply on news.ycombinator.com