Perhaps the person
who made the cock-up should be demoted to office cleaner? They might excel at that.
Red faces abound within the British Army after an Excel spreadsheet cock-up led to a number of soldiers being wrongly promoted. A screenshot of an internal email sent around the Royal Logistic Corps (RLC) and posted on Facebook revealed the snafu, which The Register has been told happened after someone in the RLC personnel …
Ahem. No. Whoever made that error should be promoted, and sent to be the British representative at the brand-new Canadian Armed Forces base on Baffin Island, a base set up just to park idiots from various armed forces of the Commonwealth and possibly allies. Britain would have one on South Georgia Island, and Australia one somewhere near New Guinea. The US would put theirs in the Mojave. Or possibly Montana. Every now and again they should exchange a few personnel.
No, do not send them to Montana. We have plenty already. We used to have Thule AFB in Greenland (sorry about Pres. Trump's faux pas there my Greenland comrades) that we sent the truly inept. Again, sorry Greenland.
We used to entice the exceptionally ignorant ones with the promise of a willing lass behind every tree on Thule. Apparently there is a notable lack of trees on said base.
If you only have one person compiling, checking, and sending out things like that - that's the problem right there. Sack the manager who put that procedure in place.
Even the basics of things like payroll and admissions should have a double-check by someone else. If nothing else, you do NOT want your processes to be in the hands of a single person (who could slip their mate through, or get run over by a bus).
Whoever *checked* it should be sanctioned just as harshly. It's easy to make a mistake, but if you don't have someone checking, it's just human nature. If you do have someone checking, they didn't do their job at all (not just made an easy mistake, but literally didn't do the entire purpose of their job).
That this went from Excel out to emails without something dry-running, then manually checking, is the problem. It's a process problem, not an individual. And, generally speaking, in my experience, the individual in this case would have been crying out for someone to help for years, because they can't be expected to compile, check and distribute emails like this without being a prize target for the slightest cockup.
I have yet to get a spreadsheet to sort properly. There's usually an objection to the number of cells selected, or to some of them being merged, without actually pointing out to me what the solution is or which cells are a problem. My usual fix is to copy and paste the data into Word, which still understands sorting.
@Daedalus
I have no problems sorting my own data. But other people's data can be difficult: most people have no idea how to make a systematic table. Especially when postal addresses are part of the table. And over the years different people have committed their own different misunderstandings.
Canadian electricity generation firm made a similar Excel error that cost it $23m once somebody realised the nature of the copy-and-paste error.
That might explain why Beer Friday at TransAlta as being every two weeks (Yes they treated us to a beer every other Friday in the Canteen) 9 years later.
That's bad. The worst I've ever encountered came during a switch replacement project, we were prepping the last few stacks, and were coming up short on our unit count. Report this issue to management, get called into a meeting to discuss the mistake. I produce all my notes, documentation, excel sheets for each stack. Turns out one of the higher ups didn't include the final stack row in the excel auto calculate for the order. The office got very quiet very quickly!
Most famous is the "austerity is good economics" paper. which is true if you forget to include all countries beginning with A,B or C in the sum().
Not enough, though this is a global issue. Like the renaming of genes like SEPT1 and MARCH1 because not enough scientists noticed the automagic conversion to dates.
I don't want to link the paywalled Nature article, but this 2016 paper is funny enough.
"
The problem of Excel software (Microsoft Corp., Redmond, WA, USA) inadvertently converting gene symbols to dates and floating-point numbers was originally described in 2004 [1]. For example, gene symbols such as SEPT2 (Septin 2) and MARCH1 [Membrane-Associated Ring Finger (C3HC4) 1, E3 Ubiquitin Protein Ligase] are converted by default to ‘2-Sep’ and ‘1-Mar’, respectively. Furthermore, RIKEN identifiers were described to be automatically converted to floating point numbers (i.e. from accession ‘2310009E13’ to ‘2.31E+13’).
"
Yeah. That. Totally not the program's fault, right? That not everybody uses excel, and maybe those who used the abbreviation first used something else (even a flat ASCII file) does of course not come to mind. I have not had to use excel until recently (you cannot do real statistics with excel, one should use a proper data analysis tool / programming language), so I am only now fighting with those brain dead auto convert things. Doesn't help that some data I'm dealing with follows formatting rules from the 70s, and those predate excel. By a lot.
(and yes, I usually use other programs, but manglement likes their excel sheets - so for real work I care sweet Få)
> Totally not the program's fault, right?
I am honestly not sure. Personally, I hate all the rather intransparent auto-conversion stuff (and stumble over it all the time) but can see the advantages of it.
Maybe some option like "highlight all automagically converted thingies" would be helpful. _I_ would love and use such a button, especially as I rarely need word/writer/calc/excel/whatever.
They've renamed the genes to ";drop table" ?
I find computers are generally pretty good. Its when you let people use spreadsheets that problems start and never end. Trying to maintain a mission critical app written in a way that makes it immune to any attempts to apply good software engineering principles or even useful backups in some cases.
I've found its often more of a time saver to re-write peoples spreadsheets in Access or web based db app than trying to get a version out of backups that had the data some idiot had deleted and now needs but trying to put that data into the current stops half the code working the day before the cheque run is never much fun and always your fault and not the company accountant who gets paid 5 times what you do for his lunches alone.
This post has been deleted by its author
And to think that the two stripes I had upon my arm once upon a time perhaps should only have been one ( or possibly three ?) . Still, the fact that the very next day, after getting the second, I pinned my best mate's ears to the wall - hard - did no harm to my reputation in the regiment as a hard man.
Then MoD really got it wrong, they commissioned me !
Chris Cosgrove
When I was in the ROC, at the time a lowly Observer at 8 Group Headquarters, I was once asked to sit in for the Post Controller (a Leading Observer position) as we were a bit short handed. I was busy fielding queries from and supplying answers to the posts, when our crew's Observer Officer took over in the Commander's position. I smiled at her and drew two fingers across my upper arm, about where the LO's Brevet would be. She glared at me and ignored me for the rest of the shift. Afterwards, she came up to me in the canteen and asked "Why did you make a rude gesture at me?". I was surprised that she'd taken it that way, and said "Oh, no, I wasn't making a rude gesture, I was indicating that I was doing a Leading Observer's job, so where are my stripes?". The following week, when I arrived for the training session, there was a brown envelope addresssed to 98052, L/Observer Purvis IC. It contained my letter of promotion and a pair of brevets to sew onto my uniform.
Some time later, on an International Exercise, I was by this time a Chief Observer (equivalent to Sergeant) and was in charge of the Tape Centre, from which messages were sent by teletype to other Group Operation Centres. We were informed that we were to be ready to receive a visit from some very top brass, including the Lord Lieutenant of Warwickshire. Accordingly, we all lined up in front of the equipment, and as my wife was standing next to me (she was a Woman Observer, and was working in the Tape Centre under me), I took her hand. The visit passed off successfully, I was able to answer the Lord Lieutenant's questions, and the party moved on. Some time later, another C/Obs. came to relieve me, and said that my presence was requested in the Officers' Room. I duly presented myself and was taken to task, "Why were you holding hands with Woman Observer Crane?" I explained that I wasn't holding hands with W Obs. Crane, I was holding hands with W Obs. Purvis. "Oh! you're married, are you, when did that happen?" "About ten days ago" I replied. "What the hell are you doing here then? You should be on your honeymoon". I explained that as the Corps, and this Intex exercise was important to both of us, we had decided to split our honeymoon into two parts, spending a week in the New Forest, then attending the Exercise, and then taking another week in the Lake District before returning to work. The Lord Lieutenant roared with laughter and said "That's what I like to see, dedication". Two weeks later my wife and I both received a Lord Lieutenant's Commendation, which was presented to us by a very sheepish Observer Commander.
Lesson #1 : When needing to compile data for thousands upon thousands of employees in order to judge promotions, use a proper database with controls and safeguards, not Excel.
But hey, this the military so the lesson will be Get Somebody Else to Double-Check The Figures.
I have a customer I see periodically who does do sorting, printing and mail-merge using Excel. The process still gives him headaches because he does it so rarely, on a variety of unconnected data, so I give him a refresher on the relevance of the steps involved. To give him his due, he is in his 90's!
Even as a staunch critic of spreadsheets, I am prepared to acknowledge that Excel is a good metaphor for *some* aspects of data presentation, but involve Word and mail-merge and it is anything but intuitive for the average man-in-the-street.
The temp they got in to do the spreadsheet that calculated what that equated to against everyone's salary's just dragged and copied 25 down the whole of the sheet. Unfortunately it was just the guy (in sales) at the top who had a 25% bonus, most of us should have got between 5 and 10%.
It took them a couple of months before they found out because everyone just kept quiet about the surprise bonus bonus in our salaries.
It took them 3 years to claw back the money that we "owed them" - every year we got a bonus letter saying, well you we due to get 6% bonus but because we gave you a 25% the other year you won't be getting it....
Beware copy and paste in general - depending on the context. I managed to shake off a 3 year business contract I no longer wanted after only 15 months because the genius who drafted the paperwork copy / pasted from a 1 year version and forgot to modify all the exit clauses. This cost them EUR50,000 and saved me almost the same amount - once the solicitor fees were paid :-D
Sadly JPA's a monstrosity built on an Oracle product by CSC. Hilariously the build contract included delivery of zero automated tests, so any modifications require some very expensive manual testing of every tiny bit of every feature.
I've seen MOD HR people use it. It's soul destroyingly terrible. Clientside Java popups pop up other popups, ad infinitum. Built by the lowest bidder, on a "deal" licence with Oracle.
Now I think about it, no wonder they used Excel.
Yeah, I used Excel once.
It was to make a VAT return for the new HMRC FETID programme.
It took three days of farting about and an 850kByte Excel macro-enabled-despite-all-the-warnings-about-it-being-dangerous spreadsheet file to send nine numbers to HMRC.
When it worked, that is, which four out of four times it didn't at the first attempt for a different reason every tome so I had to hack the fucking thing every time.
After a year of dreading having to do it again I binned it, and got something that didn't use Excel.
That worked like a charm, first time, and the CSV file for the data was a whopping 69 bytes.
Well....
the article's picture appears to be of a US soldier - can't quite tell if he's wearing RDF or Woodland in the picture, but either way its old kit (The M1 helmet went out of US service around 1985) - I'm assuming our lot are at least dealing with armed forces from the right country (though sometimes I do wonder).