You should get most (preferably all) of the resuests before you start coding. And you should get them clearly. If you start coding and accepting more and more requests you'll end up in trouble.
When you start a project, make sure it's been talked about enough, good descisions must have been made etc. Then write down what needs to be done and what the resulting software should have. Whatever is -not- in there... is too bad. They should have thought of that earlier, or pay you for all the trouble you need to go through.
With all the zombie computers, trojaned by kids or simply hacked ones it would be easy to make victims download copyrighted stuff without them even knowing it.
And so the ISPS would have to either shut down those people's accounts (even though they didn't do anything) or have loads of work to find the one who hacked the computer, and most of the time they probably can't.
Slashdot Mirror
You should get most (preferably all) of the resuests before you start coding. And you should get them clearly. If you start coding and accepting more and more requests you'll end up in trouble. When you start a project, make sure it's been talked about enough, good descisions must have been made etc. Then write down what needs to be done and what the resulting software should have. Whatever is -not- in there ... is too bad. They should have thought of that earlier, or pay you for all the trouble you need to go through.
With all the zombie computers, trojaned by kids or simply hacked ones it would be easy to make victims download copyrighted stuff without them even knowing it. And so the ISPS would have to either shut down those people's accounts (even though they didn't do anything) or have loads of work to find the one who hacked the computer, and most of the time they probably can't.