News for hackers. Stuff that matters.
Re:Why I Chose Common Lisp by chikere232 on Sunday January 12, 2025 @04:19AM (#42672283)
Very true.

Get backups

Re:Why I Chose Common Lisp by wodenokoto on Sunday January 12, 2025 @04:45AM (#42672390)
Which the client might be responsible for because the contractor might not be allowed to retain the IP
Re:Why I Chose Common Lisp by crispyambulance on Sunday January 12, 2025 @06:59AM (#42672940)
You're "allowed". Just keep it to yourself.
Re:Why I Chose Common Lisp by ska on Sunday January 12, 2025 @10:16AM (#42674143)
You often will not be, explicitly by contract. Honestly in this case it’s easier to keep things clean.
Re:Why I Chose Common Lisp by crispyambulance on Sunday January 12, 2025 @05:45PM (#42677752)
If you do some work for someone one and decide to keep the source you wrote, so you can review it later in the privacy of your own thoughts, the only way you can get "caught" is if you release it some way that's recognizable.
Re:Why I Chose Common Lisp by throw10920 on Sunday January 12, 2025 @07:12PM (#42678467)
I wouldn't want to hire anyone that thought like this, as it demonstrates a lack of morality and willingness to adhere to not just an informal agreement, but a legal contract that could expose me to liability or IP theft.
Re:Why I Chose Common Lisp by ska on Monday January 13, 2025 @06:12PM (#42690847)
If that's what you want to do, why would you ever sign a contract saying you won't do it?
Re:Why I Chose Common Lisp by crispyambulance on Monday January 13, 2025 @06:19PM (#42690920)
If the work is interesting and well-compensated, sure, I would sign that contract.

I will also keep the source I write and, if I feel like it, take a look at it years later and no one will know except me. BFD!