The correct way to handle this is to get ahold of the CTO or a relevant subordinate in their department, and inform them of the shadow-IT situation going on at the warehouse. Most risk-adverse IT executives would have a conniption at the idea that work policies are enacted by business logic code that zero employees understand and can modify.
Deleting Software I Wrote Upon Leaving Employment of a Company
41–50 of 75 posts
Re: Deleting Software I Wrote Upon Leaving Employment of a Company
#42It's more likely it'll work out like how a situation recently worked out at my employer. We had an employee that was too impatient to set up an internal AWS resource using the more time-consuming channels, so he set it up in our hack-stuff AWS account under his own user account. Our teams found it useful, and began to rely on it. He got laid off. Ops deleted all his user-related stuff, including accidentally deleting…
> too impatient to set up an internal AWS resource using the more time-consuming channels Those are by far the worst software devs, not understanding the implications of their actions. But also that his manager didn't catch up this mishap
My manager offered to give me a 2nd laptop so others could run the system as needed.
(and yes, we had kubernetes, all the fancy cloud stuff, etc)
Re: Deleting Software I Wrote Upon Leaving Employment of a Company
#43The top comment is interesting: > If you wrote this software during your working time (nine to five), and were paid for that time, then the company owns the software. I don't live in the US, but copyright laws are quite homogeneous world wide. But I do have the impression that copyright is kept as long as it is not signed over. given that the person did logistics without an employment contract, he could notice the co…
The US has the "work for hire" concept - if an employee creates work as part of their regular duties, their employer is considered both the author and the copyright owner.
For example, if you have employees take photographs of finished products, using company devices, on company time, and as part of their assigned duties, there is essentially zero question that the copyright owner of those photographs is the employer, regardless of whether this is explicitly lined out in an employment agreement.
The employment agreement definitely helps in that it preempts most disputes over what the employer's expectations are, but it is by no means necessary.
Re: Deleting Software I Wrote Upon Leaving Employment of a Company
#44Earlier quoted context omitted.
Or, if you're more of the entrepreneurial mindset, convince management of the value of the software and offer that they can pay you to keep improving it.
I agree. Put a modal in it, the trial period is over, contact x for renewall.
Re: Deleting Software I Wrote Upon Leaving Employment of a Company
#45Re: Deleting Software I Wrote Upon Leaving Employment of a Company
#46It's more likely it'll work out like how a situation recently worked out at my employer. We had an employee that was too impatient to set up an internal AWS resource using the more time-consuming channels, so he set it up in our hack-stuff AWS account under his own user account. Our teams found it useful, and began to rely on it. He got laid off. Ops deleted all his user-related stuff, including accidentally deleting…
> too impatient to set up an internal AWS resource using the more time-consuming channels Those are by far the worst software devs, not understanding the implications of their actions. But also that his manager didn't catch up this mishap
Re: Deleting Software I Wrote Upon Leaving Employment of a Company
#47Earlier quoted context omitted.
> too impatient to set up an internal AWS resource using the more time-consuming channels Those are by far the worst software devs, not understanding the implications of their actions. But also that his manager didn't catch up this mishap
It’s quite possible they understood but didn’t have loyalty to the company.
If that is the case, these broken processes will cause far more damage than that one employee.
Re: Deleting Software I Wrote Upon Leaving Employment of a Company
#48It's more likely it'll work out like how a situation recently worked out at my employer. We had an employee that was too impatient to set up an internal AWS resource using the more time-consuming channels, so he set it up in our hack-stuff AWS account under his own user account. Our teams found it useful, and began to rely on it. He got laid off. Ops deleted all his user-related stuff, including accidentally deleting…
> too impatient to set up an internal AWS resource using the more time-consuming channels Those are by far the worst software devs, not understanding the implications of their actions. But also that his manager didn't catch up this mishap