My company’s buyout has been completed, and their IT team is in the final stages of gutting our old systems and moving us on to all their infra.
Sadly, this means all my Linux and FOSS implementations I’ve worked on for the last year are getting shut down and ripped out this week. (They’re all 100% Microsoft and proprietary junk at the new company)
I know it’s dumb to feel sad about computers and software getting shut down, but it feels sucky to see all my hours of hard work getting trashed without a second thought.
That’s the nature of a corpo takeover though. Just wanted to let off some steam to some folks here who I know would understand.
FOSS forever! ✊
Edit: Thanks, everybody so much for the kind words and advice!
Please be careful when copying anything that could be considered your employer’s intellectual property (almost certainly anything you built as an employee falls into this category) off of that employer’s systems.
And definitely be even more careful about using one employer’s IP for a new employer (neither company would be pleased to discover this).
I am careful, but not concerned. The new company’s IT doesn’t give a damn about anything that I set up or implemented. Their reactions when I was describing my work and job role before the buyout was essentially, “Aww, the cute little sysadmin was making scripts and using Linux, isn’t that sweet.”
As far as they’re concerned, all the old hardware and software are e-waste and are being scrapped. They are ripping out everything, literally. From our phone system, to our physical devices, to our firewalls, network switches, Active Directory, and file server.
They are replacing every single part of our infrastructure. Everything I built is useless in their eyes.
It’s incredible how that proprietary software is actually inefficient e-waste. Most FOSS isn’t bloated or slow, but proprietary software got the high ground because of contracts and “security”, I’m sure.
I always advocate for FOSS solutions at my work, but most of the time I get shut down with some variation of “We prefer $MSP’s solution because it gives us someone else to blame if shit hits the fan”. I hate that sentiment, but I appreciate the honesty.
“But it wouldn’t hit the fan so much if we stopped using Microsoft’s half-baked products!”
It always falls on deaf ears. I can’t believe how many millions my employer throws at Microsoft every year just to complain about how broken it is.
But it’s also difficult to prove you didn’t make it similarly 2 times. Just do some name changing, reordering and some slight changes and you should be golden.
I don’t know if there’s any precedence for this, but I could see a court asking to see the git commit log if things went that far.
Depends on where you work and what their policies are. My work does have many strict policies on following licenses, protecting sensitive data, etc
My solution was to MIT license and open source everything I write. It follows all policies while still giving me the flexibility to fork/share the code with any other institutions that want to run something similar.
It also had the added benefit of forcing me to properly manage secrets, gitignores, etc
I don’t know where you are, but this isn’t always enough. If it’s your employer’s IP it’s not yours to license to begin with.
In my situation, it even extends to any hobby projects I work on and I don’t think my situation is unusual.
That said, most employers don’t care about hobby projects with no earning potential.
That seems like a good idea.
True. In my particular case it’s not an issue (because of a long and boring story I can’tbe arsed getting into), but shielding oneself as well as the employer from legal liability is important.
Very unlikely $NEW_EMPLOYER will run all your ideas past $OLD_EMPLOYER to see if it’s their code…
Will they even know if they are throwing it all away?