Vegas, baby! A Register reader gambles his software will beat the manual system
- Reference: 1617002108
- News link: https://www.theregister.co.uk/2021/03/29/who_me/
- Source link:
Today's story comes from "Paul" (not his name) and takes us back a few years to an incident that occurred amid the glitz and glamour of Las Vegas.
[2]
Paul's story starts in prosaic form. His company was bidding on a time and attendance system for one of the smaller, but rather well known, Vegas casino chains. The company had already provided the accounting department with servers and software, and so seemed a shoo-in for the employee monitoring system. The software was "tailor-made to interface to their payroll and human resources applications," explained Paul, "Best of all there were no competitors being asked to submit proposals."
"Management liked what they saw, so we installed a trial for the payroll department to review and run internal testing. Bear in mind this was our own T & A system, custom designed for casinos with an excellent history at other sites. What could go wrong, we figured?"
[3]
What indeed.
Sensibly, there was no big-bang style switch-on. The payroll was run in parallel with the existing manual system and… disaster. The figures didn't add up and the employees that would have seen mistakes in their paycheques were numbered in the hundreds.
"Puzzled," said Paul, "we carefully went over the pay calculation audit logs and found a large number of incorrect configurations on pay/time rules."
"Unions," he added darkly: "it can get complicated."
Undeterred, the gang implemented the fixes and the test ran once more.
Again, disaster. In fact, Paul's team had somehow made things worse. "Even more failures," he sighed, "many from untraceable causes, along with complaints it took too long."
So bad were things that the payroll department demanded that the code be pulled and escalated the issue to management. And so the shiny new app was summarily yanked and Paul moved on to bigger and better things.
And there the story should have ended. We've all been there – seen the latest and greatest come catastrophically undone when put into the hands of users.
Except it didn't. Fast-forward three years and the casino in question had been sold on and Paul's boss happened to be chatting to one of the (now ex) payroll clerks who had made such a fuss over the new system back in the day.
It transpired that the new system had actually worked perfectly. Too perfectly. Not only was it better than the manual system and produced more accurate results, it also took hours to run rather than days.
But those were days that the payroll department had always been all too happy to claim for overtime. Even worse was that by automating all the adjustments, the extra people normally needed to massage the figures would no longer have been required. "If the automated system had been used," Paul told us, "it would cost most of the department entry clerks hundreds of dollars a month, each."
"The reason 'it took too long' is all the time spent sabotaging the test results to ensure it would fail."
And here the story does end with a final ironic twist. Remember the selling on of the casino? The new holding company simply terminated the entire payroll department and sent processing out of state.
The reason?
"The locals were too expensive to retain."
[4]
Oddly "protecting our paycheques" is rarely given as a response to the old saying: "this is why we test" but maybe you've been the victim of sabotage by fiscally concerned users? Or perhaps you were the one creating those impossible failure scenarios? Confess all with an email to [5]Who, Me? ®
Get our [6]Tech Resources
[1] https://www.theregister.com/Tag/who-me
[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2YGGlQlyVwxrrGxOWgapX9QAAAII&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33YGGlQlyVwxrrGxOWgapX9QAAAII&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44YGGlQlyVwxrrGxOWgapX9QAAAII&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[5] mailto:whome@theregister.com
[6] https://whitepapers.theregister.com/
The "time and attendance" mentioned in the 3rd paragraph of the story. Or did the article get updated before I read it?
AKA "Clocking on" for this side of the pond.
I would expect he's referring to some of the other "entertainment" opportunities that Vegas also has a reputation for.
Was going to say other than gambling, but that wouldn't be strictly accurate in some cases either, depending on what you wake up with...
T&A - surely tomatoes and artichokes?
You don't need to be from Vagas
To have your first reaction to "T & A" be tits & ass. But then again, I was born & raised in Hollywood.
sabotage
French saboteurs would have burnt the casino down, just to make sure it wasn’t tried again.
Re: sabotage
Or kicked it with wooden shoes.
Reminds me of a friend's bollocking.
He was working in outgoing mail. You can get bulk mail discounts if you supply your mail to the Royal Mail in postcode batches. They were printing out the week's mail and then sorting it by hand into post trays for forwarding to RM. He noticed he could set 'print sorted by postcode', bingo, three days' work done in 30 minutes.
YOU FOOL!!!!! That's three days' work we can't bill for!!!!!
It's sabatoogie I tell ya!
A direct correlation between work done and pay received!
Reminds me...
... of the time we offered to pre-punch certain parts for one of our customers, like we did for most projects which always had extras in. The parts were going through our machines anyway specifically for them, all we had to do was add a tiny bit of time (seconds), provided they gave us the details. It would save them hours and hours every time.
The boss told us:- "Oh no, we can't do that. The lads come in on a Sunday to do the punching, they wouldn't be happy".
The customer is always right so we stopped arguing.
Re: Reminds me...
When I first saw this comment, I read it is "we offered to pre-punch one of our customers". Given what I am currently doing for a customer, you would have had my sympathies.
Dammit, much too early in the week!
Sabotaged by IT
It isn't always the users. I worked for one of the BUNCH back in the day and it was received wisdom that the IT departments of large organisations that were firmly in the grip of a certain large blue computer manufacturer were happy to indulge in a little empire preservation.
My first ever trip to the USA (from the UK) was to test some networking software. I met my American counterpart on the Sunday and we visited the customer on Monday. The customer was a very large car manufacturer with an IT configuration that was mostly blue, although we had a substantial toe-hold. The conversation went like this:
My colleague: "Did you make the alterations to the networking configuration we asked for"?
IT: "No. We were unsure of some of the settings you wanted".
Us: "OK, when can you make the changes"?
Them: "We update the network configuration once a month. This month's was yesterday".
We then had to fly 600 miles to an in-house machine and network we could scrounge out of hours time on.
I know of a similar example ih the UK. A household name financial organisation was a large customer of said major computer manufacturer. We'd successfully sold them a system to run a major, very public, set of financial products. All testing had completed successfully but go live day was a disaster. Turns out that they'd introduced changes to their core systems that we had to interface with. Those changes went live the day before our service did.
All too common
I've had my code rejected due to high failure rate - about 1% due to out of legal range input data. Only for it to be replaced in the long run with nearly 100 entry clerks printing out the electronic forms and double entering them and achieving a 5% error rate. An empire was wanted by the commissioner and had to tell some massive porkies about my code which had far exceeded their expectations and spec!
Another bit of code solved a commission anomaly which meant sales could work with customers to get orders of (say) 10,000 items and then return 9,995 of them and still get the commission for 10,000 items. Turned out their bosses got a large commission based their staffs commission so fuck the shareholders.
I've found many projects held up for patently spurious reasons and being able to write sql and with access to the various DBs its never ceased to amaze me the level of hanky panky going on above my pay grade. I've always felt it best not to delve too deep or point the finger too directly as people who do this can turn very nasty. I could have been very rich if I could have exploited some information I've had - or been marched out in handcuffs unable to prove my case once out of the building so I'm never quite sure whether it was cowardice that stopped me doing something though in most cases a lot of people other than myself would have been out of work for no fault of their own.
Print Union
I worked for a well known large high-value print company in the late 80s. They were developing a serial scanning system fitted to the output of a mechanical serial printer mechanism using number wheels to ensure that the printer always printed a different serial number; sometimes the next higher up wheel didn’t rotate because it had dried ink jamming it and the printed high-value “items” were printed with repeated serial numbers. Things like lottery tickets, travel cheques, etc. You can imagine the problems and financial losses involved...
Anyway, when our high-speed number scanning system detected a problem with he printed serial number it did what, can you imagine? Yes, it sounded a klaxon and flashed a light. Although it was fitted onto the printer it was not allowed to connect to the printer wiring and was forbidden from switching off or halting the printer. Union rules! Someone was paid to be in attendance and when the alarm sounded they would (eventually) put down their redtop/knitting and walk over to the printer and stop it. Then management had to bring in teams of people to sort through the printed items to eliminate the duplicates. Did I mention the printer was high-speed? In the time it took for the worker to switch the machine off, hundreds, maybe thousands of items had spewed out from the printer. Literally boxes full. All of this was Special work.
(The scanning system was cutting edge because of the high-speed paper flow causing the paper to actually fly and causing perturbations in the scanned surface.)
We made the klaxon very very loud.
"all the time spent sabotaging the test results to ensure it would fail"
And they sabotaged themselves out of a job.
Oh, the irony.
As someone who lives in Vegas, you might want to be a bit more specific about what a "T&A system" is. The first guess would not be the correct guess.