Regardless of what the client says, we have to be careful not to be factory, rubber-stamp workers. They are not only paying us to code but to give them our professional opinion. If we know, based on our expertise that something will work or not, we are obligated to tell them. Now, if having told them, they refuse and want it their way, I suggest you get it in writing and do it their way, as bad as it may seem.
Don't forget, once a site is done, it goes in your portfolio. If you just do what a client says, then you have to explain to your peers and future clients why you implemented crappy code on the previous site(s).
Finally, we have to be careful about our opinions with regards approaches to coding. Something may look "ridiculous" but by whose standards? If the experts (Chris Meyer, Alistapart, etc) say something is right based on their research and experience in the field, yet looks ridiculous to us, sorry folks, but I will go with what they say. At least they have research and facts (as opposed to personal emotions) to back it up.
I hope this helps.
|