!(Client is always right)
published on 11/3/2008 6:10:43 PM

The title of this post should be read as Client is not always right! In one of my previous projects my client used to advice me how I should implement the feature. I mean the client used to advice me on technical aspects of the feature. I have no problem listening to the client’s advice but the main problem was that the client had no idea about the underlying structure of the application.

I still remember that there was one important feature I was working on which was used to upload files to the server. The client insisted that the files should be uploaded and then assigned to all the users and dependent users at the time of uploading. I warned the client that this functionality will put immense pressure on the server and it can fail half way but the client keep on insisting.

The feature was implemented the client’s way. On the day of uploading files the application froze for 3-5 minutes per uploaded file.

So, who is responsible for this mess? I am! Even though it was client’s idea that this feature should be implemented in a certain way but I as a developer should made my case stronger and should have tried my best to push the client away from this solution.

The moral of this story is that as a developer you have the right to negotiate and let the client know your side of the story. It is better to speak your mind than to be a YES MAN.