News: 1614586513

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

Rookie's code couldn't have been so terrible that it made a supermarket spontaneously combust... right?

(2021/03/01)


Who, Me? It's March again and we're still (mostly) indoors. Let us take your mind off the long, dark teatime of the soul (to paraphrase Douglas Adams) with another reader confession in The Register 's [1]Who, Me? column.

It's back to school for us today as a reader Regomised as "Harry" regales us with a tale from a late-1990s work experience placement.

[2]

Harry had been hired by a major supermarket to work in its IT department, then based at the chain's head office.

Things were different in those days, and every store in the chain enjoyed a certain level of computing autonomy. Code updates came from the mothership and were gradually rolled out; first to one store and then to all the supermarkets in the chain.

[3]

Forget GameStop: Keyboard warriors and electronic trading have never mixed well [4]READ MORE

The IT department also had its very own version of [5]Who, Me? in the form of a wall of shame, a whiteboard in sight of the programming team listing all the cock-ups created by iffy code.

"One unlucky programmer caused frozen food to be delivered to a chilled warehouse," said Harry, "which ranked number one at the time. He no longer was in the company, he apparently fled in shame of his dire code!"

Seems a bit harsh to us but, as we said, things were different in those days. The whiteboard also had the desired effect on Harry: "As a rookie, I went 'Omg, I don't want to be on that whiteboard ever!'"

Time passed and Harry showed himself to be reliable enough that he was entrusted with his first bit of production code: a minor update to one of the in-store applications.

A supermarket was selected to be the guinea pig for Harry's first foray. He sent the code, tested it, saw that it worked, and went home. A job well done.

Except...

"Not an early riser, the next day I arrived in to sour faces and suspicious looks."

The server he'd deployed to was inaccessible. Nobody could even connect to the machine, let alone back out whatever borkery Harry had inflicted. The interrogating came thick and fast: "What code did I send down? Was it compiled to the correct machine type?" and so on.

The central system was festooned with red alerts and, although Harry insisted he really had tested his code, his elders were understandably suspicious of the rookie.

This kept up, right up until the moment, almost an hour into the grilling, that another manager passed by the meeting room and said: "Did you IT guys hear one of our stores burned down last night?"

The server had been reduced to ashes and was certainly unable to connect to the mothership.

There is no record of whether Harry's new routines featured an arson interface. Regardless, he was asked to try his deployment again, at a different store. Hopefully one with some decent fire prevention. You know, just in case.

The following morning he was not greeted with the same hostile stares. The code had worked and nothing burned down. His name would not be troubling the whiteboard of shame. Not that week, at any rate.

We can't help but note that the year before Harry's tale took place, The Prodigy's " [6]Firestarter " was topping the popular music charts. Coincidence, we're sure.

[7]

Share your coding confessions with an email to the understanding vultures of [8]Who, Me? ®

Get our [9]Tech Resources



[1] https://www.theregister.com/Tag/who-me

[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/devops&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2YDzJS64TUnXvIjJukbBXdAAAANU&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/devops&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33YDzJS64TUnXvIjJukbBXdAAAANU&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[4] https://www.theregister.com/2021/02/22/who_me/

[5] https://www.theregister.com/Tag/who-me

[6] https://www.youtube.com/watch?v=wmin5WkOuPw

[7] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/devops&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44YDzJS64TUnXvIjJukbBXdAAAANU&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[8] mailto:whome@theregister.com

[9] https://whitepapers.theregister.com/

Korev

Sad to see that even back then burnout was common in IT...

Korev

I'm not sure that is something we should be joking about really, so I'll downvote myself...

Phil O'Sophical

Shouldn't have put that HCF instruction in...

Not just me then.

tip pc

As the youngest of 4 i always got the blame for everything when i was growing up.

I still do now of course.

funny incident a few months back, something broke on a project i was on, suspicions flying that it was something i had done, bosses checking my change controls, what systems i had logged into and what commands i had run etc. The fact was, other than log in & run commands to take a look around, i had made no changes so should probably have got into some trouble for not doing any changes, but i could hardly of got into trouble for breaking the project as i hadn't made any changes at all to anything anywhere for about 2 weeks.

I think i dodged a bullet there!!

Re: Not just me then.

RockBurner

Nah - the eldest is always the one held responsible, the youngest can't possibly be expected to be aware of the consequences yet....

(eldest of 3 here)

His job didn't involve changes to the print queue did it?

Sgt_Oddball

Good old Unix printer error lp0...

Did they confirm if it was the server or office printer that immolated first?

The power of coincidence

Admiral Grace Hopper

I was working in an office that overlooked the roof of the computer hall. I was demonstrating a new piece of code that did useful things to an Oracle database. As I pressed the button to do the business, there was a rumble as the emergency generators kicked into action, the flap on the exhaust of the generator engines flipped up and dark smoke started belching out while the lights dimmed briefly as the power supply switched over. I had to spend 5 minutes convincing the assembled management that the loss of external power had nothing to do with me running a script on the Oracle server.

Re: The power of coincidence

KittenHuffer

My favourite perfect timing/just coincidence/did that really happen moment was about 3 decades ago. Walking through the pedestrian shopping precinct in the middle of Portsmouth with my ex-SWMBO. the problem being that the ex-SWMBO had a near phobia about animals (ALL animals) so avoiding the flying rats (eons of pigs!) was her prime concern. And trying to pull my arm out at the shoulder when one got too close.

For a bit of fun, I quietly said that all you needed to do was say the magic words, and when asked what they were I said "Pigeon Pie! Pigeon Pie! Pigeon Pie!". And just as I finished EVERY flying rat decided as one to leave as quickly as possible! The look on ex-SWMBOs face was priceless! (And no! There were no dogs running around, or stamping sprogs, or firecrackers going off. I really didn't see anyone or anything that set them off.)

The story was repeated by the ex-SWMBO to friends and family, and years later I would occasionally catch various relatives repeating the magic words hoping for a repeat performance.

Copmputer room shutdown

Roger Kynaston

We were having to shut all the kit down so some electrical work could be done. I had done a cron job on my SUN boxes to take them to init 0 which left them at the OK prompt. I duly entered the power-off command and with a clunk everything turned off in the room well before the Windows mob had got half way through their order shutdown process. A moment of bowel loosening panic ensued where I wondered how the test payroll server could switch everything off when the facilities guy came in and said "Good, all off then." The language from the Windows guys was not fit for the delicate ears of Register commentards.

Back in the 90's...

TonyJ

...one place I worked at fired a sales drone.

I am foggy on the details but it was some kind of inappropriate behaviour.

Apparently whilst being frogmarched off the premises (remote sales office in Bristol, I think) he was apparently furious and screamed out that he would return that night and "burn this place to the ground".

Oddly, it turned out, he kept his promise.

It didn't take long to track the genius down, either, unsurprisingly.

We had one guy who left the head office under a bit of a cloud. Nothing sackable just a clash of personalities.

The weekend after he left, someone was caught on CCTV that Saturday night filling every accessible external lock with superglue. The hoody and poor quality of the night vision made it impossible to tell who it was, of course, and no one was stupid enough to admit to it.

Made a fun Monday morning when no one could get in until a locksmith could arrive.

Oh and whilst I remember - there was a time when one French company I worked for, who had a plant in Birmingham that built trains, had said facility broken into by armed gunmen.

Nothing was taken of exceptional value but they did take a set of master keys and some IT access badges.

For some reason management thought that was ok and did nothing.

A few weeks later they returned and emptied the server room as well as a few other high value locations (most definitely inside knowledge). Management response "Well we didn't expect them to know which keys they took but we do at least know whose access cards were used..."

Re: Back in the 90's...

Rich 11

I started work at a site the same week that some incompetent in the Finance department was put on gardening leave for allegedly covering up some expensive cockup he'd made in a finance spreadsheet; it was my job to do a bit of basic forensic work (IT, not the accounting type) on his PC and the server share hosting some of the spreadsheets. I also searched the office for floppy disks (this was in the time of Windows 95) and found some unofficial backups tucked away which contained incriminating versions of the covered-up files.

There was a suspicion that Mr Incompetent would have wanted to get rid of those floppies if he hadn't been frogmarched out by Security, so it wasn't a surprise to hear the following day that he'd been spotted on camera trying to break into his office in the middle of the night. His office window was hidden from the main walk by bushes and they found jemmy marks in the woodwork, plus burn marks where he'd attempted to start a fire once he failed to break in (presumably he chose not to break the glass because it would have made too much noise). He'd clearly given up and walked away, because he was on two of the security cameras, with a hoody and baseball cap obscuring his face. Mr Incompetent lived up to his name by pulling down his hood and taking off his cap the moment he stepped off the property, providing an absolutely perfect mugshot to the camera across the road watching the gate.

Christoph

Get into work, check that the lines to the subsidiary offices are OK. Nope, one of the cards is dead, no lights showing.

Phone that office, ask the switchboard to put me through to the computer room.

"Sorry, we can't transfer calls at the moment, we've had a power cut"

"Ah thanks, that answers the question I was about to ask!"

gnasher729

One place I worked, when we all came in on Monday morning, the build server was down. They tried for an hour to contact it, until some bright spark had the idea to actually go into the server room.

He found an open window (the glass variation), an opened server, and all the RAM in the server had gone missing.

nerd pack, n.:
Plastic pouch worn in breast pocket to keep pens from soiling
clothes. Nerd's position in engineering hierarchy can be measured
by number of pens, grease pencils, and rulers bristling in his pack.