4 ms·

I saw something that was sort of the inverse of this. A teammate quit with zero notice in a 3 AM email. In that email, he indicated he'd made the decision to op

I saw something that was sort of the inverse of this. A teammate quit with zero notice in a 3 AM email. In that email, he indicated he'd made the decision to open source all the code that he had written in his last year or so with the company. It was in a public github repo in his personal account. The company had a lot of open source, but this was never expected to be part of that. We were able to get it taken down and no other action was taken against him, but it was an interesting move on his part. His motivation didn't seem to be bad blood - he continued pleasant interactions with several of us, including those in his management chain, long after leaving.

deleted 3y ago
[deleted]
captainkrtek 3y ago
Reminds me (tangentially) of when a coworker got let go, proceeded to open source code that I solely wrote (just some internal tooling), but editing the files to show he authored them. Think he was doing this to help find a new job by posting projects on GitHub. Company proceeded to contact him and the rest is history..
smcin 3y ago
Not "license to quit", "quit to license"...
em-bee 3y ago
somewhat related: at one job that was working with GPL software, i managed to get them to add a provision into my contract that stated that all code i wrote at the company would be published under the GPL. that way the company still owned my code but i would be allowed to take it and reuse it, and potentially do what your teammate did.