Ask HN: Side project might be useful for my team at work – should I share it? | Hacker News Reader

Ask HN: Side project might be useful for my team at work – should I share it?

5 pointsfinance_br06 comments

Without delving too much into details, I'm working on a developer tool that might be very useful to my team at work. How should I go about sharing it without losing my IP on it?

- I am working on it in my own free time

- I am a contractor, not an employee. Company is based in Europe. I work remotely

- It's not directly related to the company's business, it just solves a problem in the technical stack that my company uses

- I am planning on releasing it as a product in future and monetizing it

- It might save 20-30% of development time for our team at my job

Now I've heard enough horror stories about employees losing IP of their side project. Should I share (a very unpolished, early version of) my product with my team, and how should I approach it to retain all rights over my IP?

View on HN

Are _any_ of the following true?

1. You worked on this in company time? (i.e. Github history shows you did)

2. Your company asked someone (inc you or your team) to make this? (i.e. you got inspiration directly from it)

3. You worked on this on company equipment? (i.e. work provided your primary machine and you used the tools the company provided in your spare time to build this)

If _any_ of those is true, then your employer likely has a claim over the IP.

If _none_ of this is true, then you should be fine but it also depends on your employer, the culture there, and whether this is perceived as being valuable to them... YMMV.

Thank you for the answer! None of this is true as far as I'm aware. I'm also sure my employer would actually be pretty supportive.

"as far as I'm aware", this is doing some heavy lifting.

You need to be sure :)

The above list of requirements is in essence what most of the UK and EU check for when doing checks of patent and IP law.

I am not a lawyer though, I'm in engineering... so of course, get your own confidence that this approach is good for you.

Most employers would be cool with extra-curricular things (many demand it on CVs!), but you never actually know until it happens.

If you’re planning on commercializing this, absolutely do not expose your employer to it.

I thought of sharing this with my employer because:

- It will be a genuine speedup for our developer team (which I am part of)

- I will get valuable feedback from my target audience

Any elaboration of why this is a terrible idea, if I can manage to properly separate the borders between my project and my employer?

You should probably check what your contract says

Reply on news.ycombinator.com