4 ms·

I've been trying to think where else this could apply and can't come up with anything. Farm labour doesn't keep the food, factory labour not the products, shipp

I've been trying to think where else this could apply and can't come up with anything. Farm labour doesn't keep the food, factory labour not the products, shipping not the packages. Accountants not the bank accounts or company ledgers. As a programmer, code that I am paid to produce is not my code to keep. The code wouldn't exist at all if not for the particular business domain that was not mine in the first place. The example above is also about keeping public clippings of their work that they sold (were paid for). It would be like taking screenshots of a public website or something and that being okay. [added] I also don't know if they can repost a story on a personal website, I would guess the NYT or who ever would not want a paid reporter's website to steal traffic by creating a kind of fan base and probably pay the more well known reporters more than rookies because they drive viewership.

autoexec 2y ago
Chefs keeping copies of the recipes they came up with for their employers, screenwriters keeping scripts, authors keeping early drafts, musicians keeping sheet music, photographers keeping prints (if not negatives), any job where someone is expected to keep and maintain a portfolio
- 1659447091 2y ago
  Good examples, I seriously could not think of any. The difference I see is that those are works that are produced on ones own and then sold to buyers (except maybe the chef, I'm not familiar with that area.) Code, in the above context, is not created first and then sold to the business (unless its code/software one own in the first place). It is work that happens after a problem arises and then one is hired to provide a specific business domain solution.