Hacker News new | past | comments | ask | show | jobs | submit login

Indeed, this realization is hitting me slowly.



My number 1 rule when it comes to side projects is to never create something closely related to my employer's business.

As an employee, if you put a lot of your business and technical knowledge (that was acquired while on the job) on a large side project effort without your employer's consent, you're playing with fire, because you may be transferring business advantage from your employer to the outside world, including the competition. You put yourself in a position where you could even get sued if things go badly (specially if your project is a potential money maker)... See the case of the Nginx author, who just got himself into similar trouble...

In conclusion, I think your safest bet is to, as everyone is saying, talk to a lawyer... not to threaten the company, but to protect yourself and hopefully come to a friendly agreement at the end!


Could you please link an article that talks about what happened with the Nginx author?


Plenty of articles. Search for "nginx office raid".




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: