The obvious problem is that you made final payment before testing the script. With that payment you gave away all your leverage.
The time to worry about getting ripped off is now. The sqeaky wheel gets the grease, so squeak loud and repeatedly. Do it in public if they ignore you for long.
In the future, don't begin a project without a clear and detailed scope of work in writing that details payment terms. Ensure that the majority of the money is payable only when the scope of work is complete and code has been tested to your satisfaction. If a vendor won't agree to those terms don't do business with that vendor.
Why is this/. article titled 'Retailers Deploy Databases Against Customers'? The use of the word 'Against' clearly portrays bias 'against' businesses trying to protect themselves from customers who have (if the logic behind their app and the data are correct) abused the return policies of those businesses. For a moment I thought I was reading the New York Times or watching CBS...
Slashdot Mirror
The obvious problem is that you made final payment before testing the script. With that payment you gave away all your leverage. The time to worry about getting ripped off is now. The sqeaky wheel gets the grease, so squeak loud and repeatedly. Do it in public if they ignore you for long. In the future, don't begin a project without a clear and detailed scope of work in writing that details payment terms. Ensure that the majority of the money is payable only when the scope of work is complete and code has been tested to your satisfaction. If a vendor won't agree to those terms don't do business with that vendor.
Why is this /. article titled 'Retailers Deploy Databases Against Customers'? The use of the word 'Against' clearly portrays bias 'against' businesses trying to protect themselves from customers who have (if the logic behind their app and the data are correct) abused the return policies of those businesses. For a moment I thought I was reading the New York Times or watching CBS...