Which is why you always implement a dead man’s switch that you can turn off if you leave the job amicably. And never leave your source code behind if you can avoid it.
The dead man switch at one of my last places was the companies incompetence and lack of forethought.
When I left, I told them that the files for their system that I designed, built, and maintained was on the laptop I was returning to them.
They wiped it.
They also had zero clue how to use the programs I had nor any other aspect of that system so they really shot themselves in the foot then shot their other one to test of the first one hurt
Then they’ll get their lawyers involved to fuck you over. Since you probably coded it on company time with company equipment, they own everything and can sue you if you put booby traps in it. Hell there have been contracts in tech that say that everything you code while employed, regardless of whether it’s related to the business or not, they can claim, whether that extent is enforcible is another question but just the mere fact that plenty of companies are brazen enough to try that shit speaks for how much they expect to get away with, and they’re probably right.
Individuals rarely win against businesses as a design feature of capitalist society.
Well then at the very least do what I did: put in the code an Easter Egg that wishes you a happy birthday on your birthday in the copyright blurb at the bottom of the intranet page.
It is hard to get source code even from devs employed as devs in most of the world, getting source code from average office plankton is outright impossible.
The premise of this thread is someone writing code that automates them out of their own job. Even the most incompetent company is going to make sure they have that code before firing the author.
Which is why you always implement a dead man’s switch that you can turn off if you leave the job amicably. And never leave your source code behind if you can avoid it.
The dead man switch at one of my last places was the companies incompetence and lack of forethought.
When I left, I told them that the files for their system that I designed, built, and maintained was on the laptop I was returning to them.
They wiped it.
They also had zero clue how to use the programs I had nor any other aspect of that system so they really shot themselves in the foot then shot their other one to test of the first one hurt
Then they’ll get their lawyers involved to fuck you over. Since you probably coded it on company time with company equipment, they own everything and can sue you if you put booby traps in it. Hell there have been contracts in tech that say that everything you code while employed, regardless of whether it’s related to the business or not, they can claim, whether that extent is enforcible is another question but just the mere fact that plenty of companies are brazen enough to try that shit speaks for how much they expect to get away with, and they’re probably right.
Individuals rarely win against businesses as a design feature of capitalist society.
Well then at the very least do what I did: put in the code an Easter Egg that wishes you a happy birthday on your birthday in the copyright blurb at the bottom of the intranet page.
Lol you think source code you write at work is yours to take with you?
If you aren’t in a dev job it would be incredibly easy to prevent the source code from falling into company hands.
Until they sick their lawyers on you
It is hard to get source code even from devs employed as devs in most of the world, getting source code from average office plankton is outright impossible.
Now you’re just making stuff up lmao.
The premise of this thread is someone writing code that automates them out of their own job. Even the most incompetent company is going to make sure they have that code before firing the author.
Yes, even most incompetent company will try. Good luck trying in countries with working labour law.
Not paid as programmer = GTFO from my source code