Hacker News new | ask | show | jobs
by littlethrowaway 3497 days ago
I have just started working as a freelancer / contractor. It's a pretty nice deal working for a client whom I used to work for when I was in a consultancy.

Anyway, while I'm sure you-are-not-a-lawyer, if you have any advice regarding what to put in a contract I'd be keen to hear it.

The bit I'm most concerned about is the fact that it's a pretty legacy codebase, and there are almost certainly vulnerabilities I'm not aware of. At the moment I have a loosely worded (and accepted) email where I basically say "you put everything into production once you've tested it, as it's a legacy system without decent test coverage". However, I'm paranoid I'll make a mistake / it'll get hacked and then I'll get sued. Admittedly I live in a different country from the client & I am doing things through an LLC so perhaps its safe enough.

Still, if you have any advice/pointers from the trenches, I'd be keen to hear it. I honestly don't care too much about loosing a months salary, so much as loosing the shirt off my back!