My developer is not working as we agreed on the contract and now he is threatning me that if I offend him then he will make my project public before I launch the full version. I have made the contract with all the rules and NDA, but if I get into those things now, it will cost a lot of time for me which is not affordable at the position I am right now.
Is he "your dev"? How did you come to own him?<p>If your entire business is dependant on this person then they are, in a way, your defacto co-founder. But you give them no ownership.<p>The developer probably would say that you aren't holding up your end of the agreement.<p>Regardless, you can either come to terms with this person, which probably involves giving them some small degree of ownership or a more fair rate, or try to sue them.<p>By the way, I assume that you are massively underpaying them in addition to not giving them any ownership. If you were to add up all of the time the system has been in development, how many days is it? Then times 3 hours per day? And divide by the total compensation.<p>Have you been paying them at least minimum wage?
Maybe it is time to learn from the experience and start again.<p>The lessons:<p>1. Contracts are only as good as your ability to pay lawyers to enforce them.<p>2. Relationships are how things get done, not contracts.<p>3. If you are pointing at the contract, the relationship is broken.<p>4. Offending people is rarely a way to get what you want.<p>Good luck.
It might help if you clarified what he meant when he said if you “offend” him. Could you just offer to him that you just pay him any outstanding salary and then cut ties? That seems like always a fair option unless you have some contractual obligation to him. It would suck to find another developer, but that’s always a risk when hiring.<p>Or is there something else that you’re not mentioning that he’s getting upset at?
Has he signed any contract you made? Have you fulfilled your end of the deal in that said contract? Sue him if the answer is yes to both questions<p>Otherwise maybe you are the problem here?
just fire him already. the code is useless anyways if they cant execute well on it.<p>lawyering up can help but it gets complicated and time consuming if you are in different places.
You're the boss. You made mistakes. Stop. Take his perspective as far you can.<p>Do what must be done. If necessary, go public yourself and see whose attention your project gets. Adapt/pivot accordingly.<p>If he already threatened you, he's about to do it or will do it at some point in the near future, when you lost/invested even more.<p>Don't waste money you don't have and more importantly, don't waste time and attention.<p>You fucked up. It's your mistake. Own it, drink it off, adapt.