Software Engineering Stack Exchange is a question and answer site for professionals, academics, and students working within the systems development life cycle. It only takes a minute to sign up.
Sign up to join this community
I'm a freelance programmer and recently I finished a website, it all works fine but there was one user that complained to my client that he couldn't log in. This problem was clearly a cookie-restriction/old browser one (I couldn't create the problem myself and hunderds of users are working with the website just fine)
Now my client said: I've paid you to make something and somebody complains; so you didn't do your work correctly.
What can I do in this situation and how do you guys handle this?
If you haven't already done so, define the minimum system requirements of your website, e.g.
If the user did not satisfy the minimum system requirements, it's not your fault that it didn't work for him. Investigate the issue, prove that the minimum system requirements were not satisfied and send the client an invoice for the time you spent doing this.²
Of course, in some cases it's not so easy: You might be convinced that the problem lies "on the user's side", but you might not be able to prove it without putting a lot of effort into it. In that case, you should talk to your customer:
I have performed some tests, and I'm pretty sure that the problem is a weird firewall configuration/a buggy IE plugin/etc. However, to prove this, I'll have to put a lot of effort into it. If I do that and it turns out that the fault was not on my side, I will have to send you a bill for the work done by me. Are you sure that you want me to continue investigating this issue?
¹ This doesn't mean it won't work with other browsers, it only limits your warranty to these browsers. Usually, the customer will understand that you cannot test your web site extensively with every browser out there. Ideally this should be cleared up-front:
Support for IE8-10, FF12-19 and Safari 5 is included in the offer. IE7 can be included for an additional $xxx, IE6 for an additional $xxxx.
² Sending an invoice is a very powerful sign: Even if the customer complains and you end up canceling the invoice as a goodwill gesture, the client learns that unjustified complaints can cost money.
Resolve the complaint irrespective of how many users were successful. Also ensure that, through each user complaint, you record what went wrong for the future.
As a programmer, you have to consider cookie-restriction/old browser and properly account for it. There is no acceptable solution in which a 'too bad; upgrade!' is acceptable unless specified by your client.
This may be a learning opportunity in which you hash such details out with your clients to ensure, if there is the possibility, it is covered and there are no surprise 'gotcha' situations.
