BOFH: Where there is darkness, let there be a light

Where two or more idiots are gathered together, try to reduce the number of idiots


BOFH logo telephone with devil's hornsEpisode 11 The Director and the Head Beancounter are waiting for me outside Mission Control when I get to work – which is never a good thing. When two or more idiots are gathered together and all that.

“It’s about the asset register,” the Head Beancounter says.

“Didn’t we cover this weeks ago?” I ask.

“I’m not concerned about some missing equipment – I have to report the book value of current assets,” the Head Beancounter says. “We don’t have a clear picture of what equipment the company actually owns because no-one knows exactly what was bought, for whom, and what was disposed of.”

“No-one really took stock,” the Boss adds.

I suppress the urge to point out that the PFY and I took a HELL of a lot of stock, and our eBay store can attest to that.

“We may never fully know what our asset base is,” I say, shaking my head and feigning concern.

“Yes, that’s the point,” the Head Beancounter says. “We NEED to know. We have to find out exactly what assets we have so as to report a correct figure on the books. 2019–21 were unprecedented financial years and we need to be able to report the true impact financially, as well as working through our assets to see what we need to write down or write off.”

I suppress the urge to point out that the PFY and I wrote off the company van a few nights ago during a particularly rushed “stock take” and that it’s currently parked in the darkest corner of B2 on top of an ever-widening pool of oil.

“We think we need an IT inventory,” the Boss says, pausing before adding: “of everything.”

. . .

I don’t need to tell you that inventorising our IT assets is a Sisyphean task which would have even the most upbeat of people reaching for a stout cord and a wobbly chair. It’s the sort of poison chalice that tends to get handed to the most annoying of interns in the hopes that they’ll choose to exit the company without a fuss.

“Mistakes were made,” the Boss continues. “We realise there may have been some undocumented disposals, possibly some shrinkage, and more than likely some assets which were not brought into the asset register in a timely manner.”

“What gear are we talking about?“ I ask. “The stuff onsite or offsite?”

“Everything the company purchased between the first of July 2019 and the 31st of June 2021. Plus all assets on the register beforehand, along with all disposals.”

“So you want someone to check off every IT item in the register?”

“Yes.”

“You realise that it’d be cheaper for us to throw away all keyboards and mice because the replacement cost would be less than the labour involved.”

“That’s not going to work!” the Head Beancounter says. “We have to be able to assure the Board that we have all the equipment we say we have. One of them is talking about random checks.”

“In circumstances like this I generally choose the road less travelled,” I say.

“Which is?”

“Insurance fire. Douse everything in isopropyl and fire starters and set it alight. Tell the Board you were reorganising the whole building to make it more power efficient when the tragedy struck.”

“You can’t just set fire to your problems!” the Boss snaps, just as the fire alarm starts sounding.

I resist the urge to dispute the Boss’s point by taking him down to B2 to see a burning van.

A few days later …

“They tell me you’ve managed to inventory our items,” the Head Beancounter says, having been let into the server room by the Boss. “How many items did you check off?”

“All of them,” I respond. “There’s only three items left on the register: the UPS over there, the ancient Building Management server, and the espresso machine in our office – though I think that was misfiled as an IT item.”

“That’s preposterous! What about that server over there?”

“It doesn’t have an asset number on it.”

The Head Beancounter looks on the front panel, noting a sticky smear around the same size as one of the company’s inventory labels.

“You must be able to look it up by serial number!”

“It looks like the serial number has been ground off. Hey, maybe it’s stolen!”

“What about THAT server then?”

“Same! In fact, it looks like all our gear must be stolen.”

The Head Beancounter realises what the PFY and I realised several years ago – that half an hour with an angle grinder beats a couple of weeks of label checking. He’s a bit shirty, but he recognises an impasse when he sees one.

“Someone’s got to account for this. We can’t just write off all our IT equipment. The Tax Department wouldn’t buy it for a start.”

“Sure they would!” I reply. “We’ve got a huge room in the basement crammed full of old IT equipment.”

“How much equipment?” he asks, seeing a possibility to finesse himself out of a difficult corner.

“It’s a bit grim,” the Head Beancounter says, once we get down to the basement and switch the lights on to reveal masses of e-waste we’ve stockpiled over the years.

“And what’s that horrible smell? No-one’s ever going to believe that this kit is … >pop< What happened to the lights?”

I resist the urge to tell him that the horrible smell is a mixture of tar, isopropyl and diesel as I step back through the door just as he’s reaching for his lighter …

>SLAM!<

Similar topics

Broader topics


Other stories you might like

  • SpaceX Starlink satellite streaks now present in nearly fifth of all astronomical images snapped by Caltech telescope

    Annoying, maybe – but totally ruining science, no

    SpaceX’s Starlink satellites appear in about a fifth of all images snapped by the Zwicky Transient Facility (ZTF), a camera attached to the Samuel Oschin Telescope in California, which is used by astronomers to study supernovae, gamma ray bursts, asteroids, and suchlike.

    A study led by Przemek Mróz, a former postdoctoral scholar at the California Institute of Technology (Caltech) and now a researcher at the University of Warsaw in Poland, analysed the current and future effects of Starlink satellites on the ZTF. The telescope and camera are housed at the Palomar Observatory, which is operated by Caltech.

    The team of astronomers found 5,301 streaks leftover from the moving satellites in images taken by the instrument between November 2019 and September 2021, according to their paper on the subject, published in the Astrophysical Journal Letters this week.

    Continue reading
  • AI tool finds hundreds of genes related to human motor neuron disease

    Breakthrough could lead to development of drugs to target illness

    A machine-learning algorithm has helped scientists find 690 human genes associated with a higher risk of developing motor neuron disease, according to research published in Cell this week.

    Neuronal cells in the central nervous system and brain break down and die in people with motor neuron disease, like amyotrophic lateral sclerosis (ALS) more commonly known as Lou Gehrig's disease, named after the baseball player who developed it. They lose control over their bodies, and as the disease progresses patients become completely paralyzed. There is currently no verified cure for ALS.

    Motor neuron disease typically affects people in old age and its causes are unknown. Johnathan Cooper-Knock, a clinical lecturer at the University of Sheffield in England and leader of Project MinE, an ambitious effort to perform whole genome sequencing of ALS, believes that understanding how genes affect cellular function could help scientists develop new drugs to treat the disease.

    Continue reading
  • Need to prioritize security bug patches? Don't forget to scan Twitter as well as use CVSS scores

    Exploit, vulnerability discussion online can offer useful signals

    Organizations looking to minimize exposure to exploitable software should scan Twitter for mentions of security bugs as well as use the Common Vulnerability Scoring System or CVSS, Kenna Security argues.

    Better still is prioritizing the repair of vulnerabilities for which exploit code is available, if that information is known.

    CVSS is a framework for rating the severity of software vulnerabilities (identified using CVE, or Common Vulnerability Enumeration, numbers), on a scale from 1 (least severe) to 10 (most severe). It's overseen by First.org, a US-based, non-profit computer security organization.

    Continue reading

Biting the hand that feeds IT © 1998–2022