I had a recent experience that was similar in some ways to Vignesh. Being the business guy, I hired a developer (employee level not co-founder) to write a software program for me. I ran into some of the same issues as Vignesh like lack of motivation from my developer. He had taken the time to educate me about how difficult it might be to estimate how long it would take to get the software built and so I understood that it wouldn't be reasonable to judge performance based solely on results. I also didn't care what time of day he worked. However, where we ran into issues was that he was never motivated enough to put in at least 20 hours per week like he originally agreed to. Instead he would give me a maximum of 10 hours in a week and often only 5. It was very frustrating because I was expecting on him to at least meet this standard, one which he had control over. That frustration came across to him at times and only made his motivation level even worse. The relationship only got worse and worse over time and we finally ended up parting ways.
The one thing that I am very grateful for is that before I got too far with working with him, we had a written agreement signed and in place that stipulated what would happen in case of certain eventualities. This made parting ways a lot less messy than it could have been.
One other lesson that I learned is that it's critical to understand what motivates the other person. If you can't understand his motivations and what's important to him, then you shouldn't be working with him. It's a big, big problem to have a co-founder or a key employee who lacks intrinsic motivation to get stuff done.
As a related question to the HN crowd, how many hours per week is it reasonable to expect a developer to work? Is 20 hours per week too much?
The one thing that I am very grateful for is that before I got too far with working with him, we had a written agreement signed and in place that stipulated what would happen in case of certain eventualities. This made parting ways a lot less messy than it could have been.
One other lesson that I learned is that it's critical to understand what motivates the other person. If you can't understand his motivations and what's important to him, then you shouldn't be working with him. It's a big, big problem to have a co-founder or a key employee who lacks intrinsic motivation to get stuff done.
As a related question to the HN crowd, how many hours per week is it reasonable to expect a developer to work? Is 20 hours per week too much?