1,005 karma · joined June 11, 2008
Contact: paulm at mgn dot tc
Usually you want a contract to specify IP rights. You own the work you author, whether you're paid for it or not, unless you specifically transfer ownership of the IP in the contract. If you're a programmer, you may assign the IP rights of the project code to the client, but only issue a non-exclusive worldwide licence to your utility code. Similarly, if you're a photographer, you still own the actual photograph, but may specify to a client how it's legally able to be reproduced. Plenty examples abound, depending on your line of work.
Mostly, I find written contracts are WAY clearer about who gets what and when, and shows the client is at least willing to "trust but verify". I wouldn't do business without them.
Damned if you do and damned if you don't.
Usually the metrics we measure are an indirect substitute for what we actually want to measure, e.g., lines of code as a measure of programmer productivity. What inevitably happens is that behaviour is optimised for the metric, and not what the metric was intending to measure. It's really just gaming the system.
Eventually I LMGTFY. He stopped asking.
Just asking because I was in the planning stages for something and this was the first step to what I wanted to achieve. I don't know if it's worth learning Docker/Kubernetes or signing up for something like this before I've coded anything.