No, The Customer is Bloody NOT Always Right

• Want the user's credit card number echoed to the screen so they can check it for errors.
• Want the user's credit card number written to a hidden HTML form field so they don't have to re-enter it.
• Want the font size changed, when it's the user's preferences that dictate font size anyway.
• Want the user's password written to a hidden HTML form field so they don't have to re-enter it.
• Tell advertisers that banner ad graphics should be a maximum size of 200 pixels wide, when they want the ad graphics hard-coded to 120 pixels wide.
• Keep issuing change requests right up to launch date, despite being told that at least two weeks of testing will be required before launch.
• Write specifications, and then two days later tell you to do something which breaks them.
• Agree that \ is an invalid character for use in a form field, but then ask that \ be added to the error message which tells you which characters are valid.
• Want a HTML drop-down box to have configurable text input values, then go off and add "<select>" as the first option without warning the programmers responsible for input validation that this was what they intended all along.
• Ask that "Click here for option one" be capitalised "Click here for Option One" to be consistent with "Click here for option Two" [*].
• Respond to a message stating that a change to the approved artwork needs to made as a Change Request with "You've got to be joking".
• Fiddle with the database and web form designs to "get it to look right" while the developers are still working on the system.
• Obtain the access password to the development database by looking over someone's shoulder, and then go in and modify documents, then complain to the developers that they don't work any more.
• Blame the developers of their web site for known web browser bugs.
• Assign bug reports directly to developers despite being told, several times, to assign them to the project manager who will then assign them on to the appropriate developer.
• Request that the Windows "hourglass" cursor shape not be shown.
• Complain about a JavaScript bug, citing the line of code where the bug occurs and, when the code is checked, it turns out the offending piece of code was not written by the project developers, but added in after delivery by the customer.
• Re-open a closed bug report saying "No, this isn't fixed" and then go on to explain it was actually something else they were talking about and not what they entered in the bug report in the first place.
• Give a clarification of a defect report that actually makes it less clear what they want done to fix the alleged problem.
• Raise a defect report, which is fixed by the developer on the development copy of the site, then later print out a web page from the production site (which still shows the alleged defect because the production copy has not yet been updated) in response to a clarification request on another defect, and say "this page is all correct".
• Ask to be able to define the length of a 24-hour period.
• Respond to a request to "Please clarify" in a change request document by deleting the words "Please clarify".
• Decide to change the entire name of the project and web site at the last minute, when all the graphics and site text, and database names, and myriad other things have the old name buried in them.
• Ask for "Categories" and "Subcategories" to be renamed as "Sections" and "Categories" respectively in the back-end database interface only, leaving the original nomenclature unchanged for the front-end web interface.
• Give you a sample product database to test your code on, which has several fields which should equal each other defined as strings which differ by leading zeroes.
• Give you a sample product database with one of the essential database table constraints disabled, so they could enter fake data that doesn't obey the same rules as real data.