Earlier quoted context omitted.
This is not a good analogy. A substantial chunk of the value of software is often the idea, not only the time worked on something. Ideas and inventions don’t happen on a schedule. Think of a chemist that is tasked with finding a way to synthesize a compound. He tries all day at work, and in the evening, on the couch, he’s struck by a bolt of enlightenment. Who does that idea belong to? German law would be pretty clea…
> And often, software is similar. That only holds if the side-project is exactly what the company does, and even then it’s debatable: if a person is interested in problem X and has personal projects around X, and the company hires them because if that, do they really expect that person to stop being interested in X on a personal level?
> if a person is interested in problem X and has personal projects around X, and the company hires them because if that, do they really expect that person to stop being interested in X on a personal level?
This is exactly where you start entering a problematic grey area. The employer hired and pays the employee exactly to gain access and make use of that knowledge and interest and pays a wage exactly for that. And at the same time, the employee wants to continue working on their open source project, giving away exactly that knowledge for free, which potentially diminishes the value that the employer pays for. There’s a fundamental tension here which is difficult to resolve. Open communication helps, explicitly spelling out the boundaries as well. It’s impossible to tell from the tweet which side failed here to what degree, but getting a sign-off from management in edge cases is definitely a good idea.