4 ms·
Just to add to the other comments here, from a more freelance perspective: Most work for large corporations is done under a "work for hire" agreement which mea
by noduerme 5y ago
Just to add to the other comments here, from a more freelance perspective:
Most work for large corporations is done under a "work for hire" agreement which means the company owns the copyright to the source you write. Additionally, many big companies will pressure you to accept employment clauses that claim ownership of anything you create in your free time, 24/7. This is not just for code, it's also standard for contract employees in the TV and film industry.
Note I'm distinguishing here between "employee" and "freelancer". I refuse to sign work-for-hire agreements, which means when hired, I still own the copyright to the source. I grant the company hiring me free use and modification and in some cases, right to resell.
I had a case of a startup where I was the sole coder, who turned around and sold their app to [Fortune 100 company] who didn't realize that I still owned this source. This company then asked me to consult - offering half what I'd been paid to write it - and further, asked me to sign a contract stating that they owned the code and everything else I made while I was consulting with them. Oh and also, without my help, they were missing some major assets they needed to recompile it.
I told them where to stick it, so they hired a bunch of people to try to reverse engineer it rather than agreeing to my terms. That didn't work (not least because I had trapped the fuck out of the code they did have, in ways that made it crash the compiler) so they ended up down a couple million bucks and shuttering the site. If they had only been nice, and hadn't come at me with the aggressive attitude, it could've been a nice little asset.
If you do not sign a work-for-hire agreement, and you're an independent contractor - not an employee - you own the source code unless otherwise stated in a contract. Beware that some jurisdictions will view you as a de facto employee in some cases (for better or worse). And my advice to anyone listening is, never, ever sign a contract with one of these companies that stipulates that they own your off-time work product. It's completely abusive and unnecessary. It's not worth taking a job with such a company.
- eloisius 5y agoSo you wasted their time and money writing “traps” in the code? Sounds really unethical.
- arthurcolle 5y agoYou sound like someone that owns a lot of equity at the place you work at - congratulations! Bellum omnium contra omnes
- eloisius 5y agoIf by the place I work at you mean nowhere, yes I own a lot of equity there. But in my past employment and contracting relationships, equity or not, I can't imagine shipping code with kill switches or booby traps that weren't in the spec or otherwise requested by the person I was working for.
- ipaddr 5y agoWelcome to the world of business. Usually the developer gets taken advantage of because they assumed the world to be fair and equal and companies to have your best interest. In this case the developer got wind of an attempt to take advantage of him. He put in protection to prevent this. That's what a company would do. To not understanding why someone needed do that strikes me as a bit naive.
- noduerme 5y agoTo be fair, the kill switches were mostly to prevent decompilation and reverse engineering. And I added them on my own time after I learned of the pending sale, which no one had consulted me about, and before the company took control of the servers, which I was administering. Was it worth my time? Absolutely. The people who sold the company intentionally misrepresented what they actually owned. They only owned the final compiled software they had purchased, and the right to use and repair or modify it. They didn't have a right to sell the source code, and I had no obligation to make it easy for the buyer to reverse engineer it.
- laurent92 5y agoLesson learnt: If I had consultants, I’d ask for open-source delivery. Which has the side-effect of also advancing humanity, so we all win.
- rambambram 5y agoPerfect! Possession is nine-tenths of the law. Pacta sunt servanda. You made a good deal about something you created, and you had the powerful means to enforce the deal. I like that. People can say this "sounds unethical", but this is exactly what every other employee or freelancer should aspire.
- eloisius 5y agoYes, it's nice to have it _when you need it_, but consider all your other honest customers that years later discover your kill switches littered throughout the code they paid you to write. They'll have to pay some other developer to untangle or work around them. If your contract with your customer doesn't include a provision for the them, or it wasn't on the roadmap you worked out with your customer, you're delivering them something with defects that may cost them later. To say nothing about how they will feel about you once they discover you anticipated that they were a cheat the whole time you worked with them. Paranoia-driven engineering decisions like this are no good. If your customers are bottom-of-the-garbage-can customers, get better customers. If you can't find better customers, then perhaps you are right where you deserve to be, doing garbage work for lousy cheats, which you must booby trap to make sure you get paid. If that's where you are, fine, but I hope no one with a brighter future reads these kinds of comments and thinks that being a bottom feeder is the norm.
- rambambram 5y agoI might have misread the comment. I was under the assumption that a business deal went wrong, and that the programmer never ceded ownership of the source code to begin with. Ofcourse, preventing is better than healing. But if you happen to make a deal and the other party turns out to be illegally selling something that's yours, than it is better to be able to enforce that deal.
- noduerme 5y agoI think you may be misunderstanding my position. To be clear, the original company owned the functionality they were purchasing. They needed software that did X, Y and Z. A lot of the code that went into it was code that I had already written for other purposes, including my own projects. They never owned that. They then sold the company as if they owned it - i.e. as if the purchaser would have free access to the source to repackage as they liked. I had no such contract with the original company, much less the buyer. I should also clarify that this was a PHP backend that was handed over freely, and a public-facing Flash app that was handed over as an SWF. At heart it was a highly specialized video / social platform. Graphics assets were handed over. What was not handed over were the front-end AS3 scripts; and I used a few hex editing methods and other ways to trap the compiled bytecode that would crash all known SWF decompilers. I also had it phone home if someone tried to decompile it. (All those decompilers would start by importing the SWF onto the root object of another SWF; root detects a higher parent; kaboom). What those guys did, and what the other company tried to do to me, was unethical. I didn't even have the right to sell them exclusive use of some of that source, because it was already deployed in other commercial projects. I didn't have the right to sell it out from under the other companies who already had paid for use of it. My refusal to sign [Fortune 500 company's] contract was on their behalf as well as my own. That company wouldn't listen to reason, so I left them a working binary and said "good luck", and then watched it keep phoning home until they gave up trying to decompile it. Also, I've never prevented an honest customer from accessing source code they needed, and in this case I was willing to negotiate a non-exclusive use of the source code with the new company, for a fair price. But they refused that. They demanded sole ownership for $0, and they wanted to pay me half my rate for consulting. Not to mention they themselves are one of the most blatantly unethical companies in the world. I didn't feel like I owed them anything.