3 ms·
on the other side of the coin, Take Two just killed an indie studio that was refusing to cede control over ksp 2 development direction by poaching the majority
by LoSboccacc 6y ago
on the other side of the coin, Take Two just killed an indie studio that was refusing to cede control over ksp 2 development direction by poaching the majority of its employers
not saying non-competes are straight up good, but it's not that they exist in a vacuum because every employee is the evil guy from monopoly.
I like the solution that we have here, non competes without monetary compensation are immediately void. so if they want to handcuff you, they have to pay for it after employment for as long as they want the non compete to be enforceable.
it's a minor simple thing, but haggling on the non compete handout is much easier than trying to get the non compete removed.
- 0az 6y agoI believe in this case they also killed the indie studio's contract.
- steventhedev 6y agoThere's a vast difference between a noncompete agreement between employee and employer and a noncompete/nonsolicitation clause in a contract between businesses. The first limits the individual employee's ability to compete in the marketplace. The second prevents a business partner from leveraging their position to kill your business. Almost everyone (except the shareholders) benefits from employer-employee noncompetes being banned outright. Almost everyone suffers from having business-business nonsolicitations being banned outright. Why the studio's lawyer didn't include it in the contract is beyond me...
- hodgesrm 6y agoI've been in the DBMS business for three decades and have never heard of this happening. In California it's a vanishingly rare case. What has happened is that every new DBMS company I know has benefited from the flow of engineers from legacy companies. This would have been impossible with non-competes. Happy to be proven wrong.