This is a discussion on Wide vs Long tables within the MySQL forums, part of the Database Server Software category; --> On Apr 11, 12:48 pm, gor...@hammy.burditt.org (Gordon Burditt) wrote: > What's wrong with choosing WHAT THE CUSTOMER TOLD YOU? ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| On Apr 11, 12:48 pm, gor...@hammy.burditt.org (Gordon Burditt) wrote: > What's wrong with choosing WHAT THE CUSTOMER TOLD YOU? > Why do you think you know his address better than he/she does? Cuz customers is morons. A co-worker just relayed to me a story about one of our customers, who ran a report on the legacy system first thing in the morning. Of course, they continued working on the legacy system all day. We transferred the data to the new system in the afternoon. BUT; when they ran the report on the new system, it came out -- DIFFERENT -- You don't suppose that USING the system in the intervening hours CHANGED anything? Nah, couldn't be -- must be a bug in the new system somewhere -- Customers -- can't live with 'em, can't live without 'em -- :-D |
| |||
| >> What's wrong with choosing WHAT THE CUSTOMER TOLD YOU? >> Why do you think you know his address better than he/she does? > >Cuz customers is morons. I'm talking about "customers" as in "customers of the business", not "the business that hired you as a DBA consultant". A person giving you their own address, assuming they are not trying to scam you, and especially if they just paid for something to be shipped to that address, probably knows it better than you do. >A co-worker just relayed to me a story about one of our customers, who >ran a report on the legacy system first thing in the morning. Of >course, they continued working on the legacy system all day. We >transferred the data to the new system in the afternoon. BUT; when >they ran the report on the new system, it came out -- DIFFERENT -- > >You don't suppose that USING the system in the intervening hours >CHANGED anything? Nah, couldn't be -- must be a bug in the new system >somewhere -- I had a big problem like that once. We were doing a large migration. We expected a SMALL number of differences (a few hundred, and in fairly innocuous places, like change of email address). We got a HUGE number of differences (tens of thousands). It turned out that, contrary to the migration plan, that billing had run on *BOTH* systems (should have been neither). Can you say "double billing"? Further, they were about to re-do the migration and run billing AGAIN. |
| |||
| ThanksButNo wrote: > On Apr 11, 12:48 pm, gor...@hammy.burditt.org (Gordon Burditt) wrote: > >> What's wrong with choosing WHAT THE CUSTOMER TOLD YOU? >> Why do you think you know his address better than he/she does? > > Cuz customers is morons. > I feel your pain and while it's severely OT here, I'd suggest that you look at the theories being propounded by the "Extreme Programming" guys. Regards |
| ||||
| Gordon Burditt wrote: >>> What's wrong with choosing WHAT THE CUSTOMER TOLD YOU? >>> Why do you think you know his address better than he/she does? >> Cuz customers is morons. > > I'm talking about "customers" as in "customers of the business", > not "the business that hired you as a DBA consultant". > > A person giving you their own address, assuming they are not trying > to scam you, and especially if they just paid for something to be > shipped to that address, probably knows it better than you do. > >> A co-worker just relayed to me a story about one of our customers, who >> ran a report on the legacy system first thing in the morning. Of >> course, they continued working on the legacy system all day. We >> transferred the data to the new system in the afternoon. BUT; when >> they ran the report on the new system, it came out -- DIFFERENT -- >> >> You don't suppose that USING the system in the intervening hours >> CHANGED anything? Nah, couldn't be -- must be a bug in the new system >> somewhere -- > > I had a big problem like that once. We were doing a large migration. > We expected a SMALL number of differences (a few hundred, and in > fairly innocuous places, like change of email address). We got a > HUGE number of differences (tens of thousands). It turned out that, > contrary to the migration plan, that billing had run on *BOTH* > systems (should have been neither). Can you say "double billing"? > Further, they were about to re-do the migration and run billing > AGAIN. > > <G> That's one way to pad the piggy bank! -- ================== Remove the "x" from my email address Jerry Stuckle JDS Computer Training Corp. jstucklex@attglobal.net ================== |