News for hackers. Stuff that matters.
Re:Expedia on how one extra data field can cost $12m by gaius on Tuesday November 02, 2010 @08:47AM (#1860190)
To be fair there's absolutely no frickin' way that you could predict that people would enter their bank in place of their employer.
Re:Expedia on how one extra data field can cost $12m by eitland on Tuesday November 02, 2010 @09:10AM (#1860257)
No, but there should be some way or another that those who create large, international websites should know that their websites are going to be used by non native english speakers :-)

Still there is lots of web forms with a Country field and a State field. And in the state field you'll only find American states.

Re:Expedia on how one extra data field can cost $12m by whatusername on Tuesday November 02, 2010 @09:24AM (#1860297)
Or 5 digit "zip" codes.

// I wonder how many Internet residents live in 90210? I know I do in a couple of places.

Re:Expedia on how one extra data field can cost $12m by smiler on Tuesday November 02, 2010 @10:13AM (#1860456)
:) Yup that is my standard zip code when I need it. What I find even more frustrating is that some US stores ask for your zip code when you make a purchase. (Is it ok to refuse?). Being English, I just state that I don't live in the US, but it's not a practice I've ever encountered in the UK.
Re:Expedia on how one extra data field can cost $12m by kenj0418 on Tuesday November 02, 2010 @10:54AM (#1860632)
It usually confuses them if you refuse. When they ask, I live in the zip code 90210 and my phone number is 867-5309.
Re:Expedia on how one extra data field can cost $12m by cullenking on Tuesday November 02, 2010 @11:30AM (#1860809)
Oh that was mean mean mean. I don't know how long it will take that song to leave my head now :(
Re:Expedia on how one extra data field can cost $12m by CapitalistCartr on Tuesday November 02, 2010 @11:32AM (#1860819)
Yeah, I usually refuse, and they simply enter 99999 or some such. It's only for marketing research, so they don't actually care.
Re:Expedia on how one extra data field can cost $12m by pmjordan on Tuesday November 02, 2010 @03:26PM (#1861923)
It's happened to me in the UK (and in Austria) from time to time. Mostly seems to be shops with a relatively large catchment area. (something like Ikea, though I'm actually not sure they have ever asked me) Asking for the UK postcode is of course pretty sinister as it narrows it down to a couple of houses. Sometimes they only ask for the first bit. Based on the reactions I've received, I doubt many people opt out.
Re:Expedia on how one extra data field can cost $12m by tomjen3 on Tuesday November 02, 2010 @07:06PM (#1862816)
It happens in Denmark quite a lot, but I usually just give them a real zip code I don't live in.
Re:Expedia on how one extra data field can cost $12m by RyanMcGreal on Tuesday November 02, 2010 @09:16AM (#1860273)
Exactly, which is why review and testing is so important.
Re:Expedia on how one extra data field can cost $12m by CWuestefeld on Tuesday November 02, 2010 @10:11AM (#1860448)
In the abstract, this ought to be obvious.

But as it relates to this specific example, I don't see how to test it. Surely you're not going to just randomly remove fields from forms, to see if anything good happens. The only way I can see to deduce this particular problem would be if the site is storing all of the failed checkout entries. And I think that's the wrong thing to do in this case, because of the privacy implications

Re:Expedia on how one extra data field can cost $12m by ig1 on Tuesday November 02, 2010 @01:14PM (#1861336)
Who doesn't store failed checkouts ? - I can't see why you would consider that any more of a privacy violation than storing successful transactions.

Especially in the travel industry where credit card fraud is very high, storing failures is important for auditing/anti-fraud activities, not to mention customer support.

When a customer calls you to say "my transaction failed", and you respond "We don't have any record of your transaction" at best that makes you look unreliable and at worst the customer thinks you're calling them a liar.

Re:Expedia on how one extra data field can cost $12m by CWuestefeld on Tuesday November 02, 2010 @02:39PM (#1861718)
Who doesn't store failed checkouts ? - I can't see why you would consider that any more of a privacy violation

It seems to me that a common failure mode would be entering a value into the wrong field, and that includes putting the credit card number into address or something. I want to do everything I can to avoid storing a credit card number (except for the one place it's saved, encrypted, at the customer's discretion).

Re:Expedia on how one extra data field can cost $12m by qjz on Tuesday November 02, 2010 @03:01PM (#1861815)
The process doesn't have to be random. Nobody likes to fill out forms, so the goal is to make them as simple and short as possible. What value did "Company Name" add to this form? Someone thought it would be a good idea to collect this data, but I wouldn't be surprised to learn that it was never used in any way that contributed to the bottom line.
Re:Expedia on how one extra data field can cost $12m by lukasz on Tuesday November 02, 2010 @04:50PM (#1862288)
Well, the testing of that form might have been as simple as asking few people (ex. clients) to buy something and watching as they performed the task (and how they fill in the form). It could have been arranged for a few bucks less than that $12m. That magic approach is called usability testing.
Re:Expedia on how one extra data field can cost $12m by staktrace on Tuesday November 02, 2010 @10:21AM (#1860489)
On the other hand if they weren't trying to gather as much information about users as they possibly could this wouldn't even have been a problem in the first place. What possible benefit does an optional "Company" field provide?
Re:Expedia on how one extra data field can cost $12m by patio11 on Tuesday November 02, 2010 @10:26AM (#1860510)
"It would be great if we knew what percentage of our customers were business travelers. It would really improve marcomm.". "The web guys say they can ask, it won't take five minutes.". "Brilliant! Do it. Next order of business..."

Six years later, nobody has checked the form since. After all, that isn't their job.

Re:Expedia on how one extra data field can cost $12m by gaius on Tuesday November 02, 2010 @10:26AM (#1860511)
In the event that there are several companies sharing the same address. E.g. my address here is <name>, <company name>, <building name>.