It's quiet. Possibly too quiet - The kind of quiet you get when you shove a thick chunk of copper wire in a circuit breaker, a nail in the phase circuit breaker and a bolt in the floor circuit breaker... then drop a screwdriver down one of the ventilation holes of the mainframe's power supply.

I make my way carefully through the emergency-lit computer room to my office, my only detour being a quick circuit breaker replacement tour and a stop at the bin to drop off a badly scarred screwdriver.

I always prefer to start the year off with a bang - or, to be more precise, a series of loud hums, a crackle or two, and a muffled BOOM from the sub-basement.

After all, it's just good manners to let the great unwashed know just who's still at the helm of this operation.

The PFY, meantime, is on holiday, exercising his Christmas bonus to its maximum potential. After all, it's only a matter of time before the Boss realises that there's a duplicate of his credit card out there (again) and calls up the card company.

I did my bit for the PFY's R&R by pushing the Boss's latest credit card statement, envelope and all, into the shredder. Apparently he was under the misguided impression that receiving mail at work is far safer than getting it at his dockside apartment drop box... a mistake that's likely to cost him.

Speaking of the Boss's mail, it's about time to distribute all his waylaid Christmas vendor freebies among the IT troops in a manner not altogether unlike a modern day IT Robin Hood.

"What? Is that it?" a particularly ungrateful antipodean contractor (who couldn't find his bum with a mirror and a torch without a 1:1 scale map) asks after I hand him a bottle of red wine that has better disinfectant than drinking properties.

"Sorry?"

"It's a little, er, cheap, isn't it?" he sniffles.

The things you hear when the PFY isn't around with a nailgun.

"Gee, sorry Mike!" I cry. "I guess it's not like home where you get your pick of the flock for the night as a Christmas bonus."

He lets the slur pass, and grudgingly accepts the bottle, not realising just how well I remember the time, after an agency knees-up, when he dropped me off at the farthest tube station from my destination...three minutes AFTER the Tube stopped running.

Trusting no one, he stashes the bottle in his desk-side footlocker, giving me the chance to stuff a large piece of foam packing over the cooling inlet at the back of his desktop machine.

Thermal overheating time bomb set, I wander off to distribute more New Year cheer.

And not a moment too soon, as the power is restored and the building springs back into life.

When I've run out of blocks of foam and cheap bottles of wine, I grab some of the good stuff and go on my REAL goodwill rounds, dropping off gifts to the telephone operators, the cleaning staff, and, lastly, the building maintenance guy. Know what palms to grease and when - that's my motto.

Having ensured that no one's going to investigate my long-distance phone bill, find the Boss's shredded credit card statements or wonder what's protected by the Armageddon-proof lock on the door marked 'Plant Room No3' in the basement, I return to my office.

As luck would have it, the Boss is waiting for me there with an annoyed expression on his face. It's only a 'generally-annoyed' expression, which means that he's probably not found out about his credit card yet, let alone me calling up his credit company and cranking his limit up so far he'd get nose bleeds just thinking about it.

"What's this about you blocking up the cooling vent of Mike's machine?" he asks.

Bastard!

"Oh, that - it's not sponge, it's...noise damping material."

"?..."

"Noise damping - the material has a gaseous porosity which allows air flow but reduces sound output by a factor of around 10 decibels per megalitre of vacuum-rated European Standard air."

"Err, really? So it's just to cut down noise?"

"Of course!"

"Hang on a minute!..."

I suppose it was a little too good to be true...

"Yes?"

"Why haven't you installed any on my machine?"

I don't believe it...

"Oh, I was just getting round to it - your one is in that old monitor box over there."

He ferrets around in the aforementioned box before pulling out a bit of packing.

"This? It's a bit of machine packing."

"No, it's a sound-reducing, air-cleaning filter."

"Then why has it got 'recycle this packing carefully' printed on the side of it?"

"Because... it was packed in old newspaper and they couldn't print over the top of it."

"Oh... so how do I use it?"

"Well, you make sure that it's hard up against the fan inlet so that no, er, 'unfiltered' air can get through."

"Right, well, I'll let Mike know then," he burbles as he wanders out to destroy his machine.

"No, no!" I cry. "Leave that to me - I'll sort him out."

And sort him out I will.

Thursday. Pay Day. I love Pay Days. In fact, work is always better on a pay day. People are nicer, complaints are rarer, bank managers are friendlier - a guy could get used to this.

A bastard, however, could lose the touch - that finely honed reflex that enables him (or her) to sort the wheat from the chaff (user-wise). Complacency is the enemy.

Still, the brown envelope containing a cheque is a useful reminder of what we do this for. Smiling happily, I fumble with the self-adhesive seal on the envelope (the glue must be the same stuff they use to hold tiles onto the space shuttle), before losing my patience and ripping the envelope open from the other end.

Ahhh!, The smell of a freshly printed cheque...the feel of it as it slips out of the protective environment of brown paper. The temporary but overpowering feeling of goodwill for all things beancountery as I note the aesthetically pleasing sight of my company's name laserprinted on the top line, right above the amount of...WHAT THE HELL!?

THE THIEVING BEANCOUNTER BASTARDS HAVE UNDERPAID ME!

I have another look, just to make sure I've got it right. "The beancounters have underpaid me!"

"You're joking!?"

"I'm not! Look, they've rounded down the amount!"

"By how much?"

"27p!"

"Hang on, you're going to maim someone - possibly permanently - over 27p?"

"It's not that it's 27p, it's the principle of the thing. STEALING from me! It's unheard of! It's the thin end of the wedge - before you know it, they'll be riding the lifts again. They'll be questioning your expense claims, talking to you about business plans at lunchtime, and..."

About 10 minutes later I come to, with a rather nasty bruise on my head and a pain in my side.

"Sorry about that," the PFY calls from behind the door of the computer room, waving one of our low-output (aka 'warning') cattle prods.

He must have zapped me while I was under the influence of theft-crisis. "That's OK," I respond, "perfectly acceptable under the circumstances."

I go to let myself into the computer room to assure him there are no hard feelings, only to find my access card's been given 'lock-out' status.

"Sorry about that, too, but you know what you get like," the PFY calls through the safety glass.

"Of course!" I cry "No harm done," as I sneakily reach for my special reserve access card, noted in the database as a 'Fire and Civil Emergency' access card, which no one but me knows exi...

"Got that one, too..." the PFY murmurs apologetically.

You've got to give him credit, he's a chip off the old block.

I move away from the door to see if he's going to come out when he thinks it's safe, but he's not that stupid, either.

Desperate times call for desperate measures. I set my rubbish bin on fire, then reverse the direction of the office ('remodelled') air-conditioner so that it's blowing air into the computer room instead of stealing air from it.

The halon 10-second warning goes off and the PFY rushes to the hold-off switch - the real one (disguised as an intercom pager button) - and not the decoy we use to frighten contractors.

I have him right where I want him. While the smoke detectors still sense smoke the halon system is still activated. While he holds the button down, the halon countdown is paused. Currently at seven seconds...

I hold the rubbish bin up to the viewing window and throw in some more paper and a back-up tape (to keep it nice and smoky) so the PFY can see I'm serious.

Out of earshot, he scribbles a quick note on the wall. "You could be right, 27p is an insult!"

Smiling, I pour coffee into the bin to extinguish the flames, then sit down at my desk. The PFY emerges from the computer room once the halon clear has been signalled.

"So, what are we going to do?" he asks.

"Well, I thought some form of example has to be made. Firm - but not, of course, brutal."

"You mean chilli sauce in the eye-rinse bottle, laxative in the water fountain or glue on the bog seats?"

"Well..."

"All three?"

"Warmer..."

"'Route their traffic via the 3-Phase mains 'network'?"

"Almost there..."

"Put indelible dye in the rooftop water reservoir and trigger the sprinkler system on their floor?"

"Yes...to all of the above."

And so it was that half-an-hour later, the PFY's up a ladder, pouring a crimson cement dye concentrate into the reservoir, when...BDZZZT!!

To his credit, the PFY makes no sound as the cattle prod takes effect. Apart from the splash of course.

After I've fished him out, I disable his card, the halon system and the card known to the database as 'Installation Card (Disabled)'.

What goes around comes around.

The boss is going on about Disaster Recovery again, like the company's going to go to the wall if one of the buildings collapses in an earthquake or something. My comment that an earthquake during work hours might actually improve the company's performance did not generate the expected chuckle of assent.

One more for the seismic therapy in other words. And, as part of his enquiries, he wants to inspect all our DR planning and see just how well prepared we are for the eventuality.

I could tell him the truth, which is that we're about as prepared for disaster as Butch Cassidy and the Sundance Kid, but that would cause a lot of very unnecessary concern.

Not to put too fine a point on it, I told him a load of old bollocks. Certainly enough to satisfy middle-management types in any case: "Oh well, we're completely prepared with off-site media and media inventories - back-up recovery plans, disaster recovery agreements with hardware manufacturers, along with three 'cold-site' venues in our distant offices to run up a recovery system in about 36 hours, give or take half a day or so," I burble.

"Add to that our redundant cabling links, agreements for emergency cable and satellite service from the major carriers, the network side of the recovery would be the simplest part. The slowest bit would be reading the tapes into the various server machines. Client and desktop machines would be added on an as-needed basis, depending on the employees concerned and their immediate importance to the company plan."

"Excellent!" the boss cries, eyes shining with delight. "Well, I suppose all that's left is for a quick tour of the facilities!"

So now I'm up a thinwire without a terminator. The boss is bound to find out sooner or later that it's all bollocks and demand to know why.

The PFY notices my air of resignation (to having to listen to the boss rabbit on about 'professional integrity' and not job evacuation) and asks what the problem is. I fill him in on all the sordid details.

"We could just take him to one of the cold site centres and tell him that they all look like that, then get the off-site media bloke to say that they don't permit site visits," he suggests.

"The media guy might work, but the cold site's a goner."

"Too cold to be fired up?" the PFY asks.

"No, too hired out to other tenants."

"What?!"

"Well, they're normally right in the heart of the business districts. So I usually rent the space to some other company and pour the dosh to a more deserving project - in this case boosting the bandwidth of the outgoing network connections."

"Uncharacteristically altruistic of you," the PFY murmurs.

"Yeah well...But it's all over now. He's bound to..."

"Not necessarily!" the PFY shouts with satisfaction, with what looks like a glimmering of a plan in his eye.

Two days later, the boss joins me in the back of a limousine for the trip to our site. "Bloody dark in here," the boss mutters. "Can't even see out the windows."

"Yes," I ad lib. "This is a loaner from the Media Storage place - they take no precautions as they have important clients."

"Oh," the boss utters smugly, self-importance boosted. "So, where are we going?"

"We're going to the nearest site, which is about two hours away. I thought we'd tour one site a day if that's OK with you."

Two hours later we glide down a ramp into the sub-basement parking area of the first DR centre. I help the boss into a newly refurbished freight elevator (security reasons) and we drop a level to the DR centre.

"Reminds me of somewhere," the boss mumbles, slightly more confused than his normal operating level.

"We got the DR centres to look familiar so that relocation and orientation is easier on the staff."

"Really? That's quite a good idea!"

We enter the DR computer room and have a quick look around. "It's a bit quiet isn't it?" the boss asks.

"Well, cold sites are typically only fired up in an emergency - mainly to save power and maintenance costs."

"Of course."

The rest of the tour goes smoothly and we make our way back to the office.

"Where to tomorrow?" the boss asks.

"I thought we might leave early and get to the Welsh Centre...pick you up at your place at 6am if that's OK."

Once the boss has gone I tap on the driver's window. The PFY's visage appears as the smoked glass descends.

"Wales tomorrow," I murmur. "Move the kit around a bit, put some Welsh maps up with coloured pins at strategic points, and leave a box of leeks in the freight elevator. Oh, and for Pete's sake, get a bit more of the city in, will you? Two hundred times round the block is just asking for trouble!"

Right, now to translate some machine names into imitation Welsh for the boss's edification (i.e Clomputhenay, etc.).

This DR Stuff - it's all work, work, work!

However, there is little philanthropy in this act, but more opportunity for a little hell-raising. I'm so bloody nice, I deserve a medal! Out of the kindness of my heart, I have volunteered to look after the helldesk in their time of need. It appears that thanks to winter chills and staff holidays, the helldesk is chronically understaffed.

The PFY, bless him, is cut from the same selfless cloth as myself and has offered to keep watch for - I mean, assist me in looking after - the users.

Nothing much has changed since we were here last. Well, it is daytime now, and I'm not carrying a sack and a crowbar, but apart from that it's pretty much the same.

"This," I say to the PFY, "is a telephone. You've seen people talking at them before, and now it's your turn to give it a go."

I ignore the PFY's hand gesture which, under normal circumstances, would denote something to the effect that "you have a sexually fulfilling relationship with your right hand" (which, incidentally, I have interpreted as, "I am in desperate need of a damn good kicking - perhaps you could see your way clear to organising me one in the near future?") and get back to the job at hand.

"You take lines 1, 3 and 5. I'll take 2, 4, and 6," I snap.

"What? I thought we were just going to divert all the calls to the Religious Thought-for-the-day message line and rifle through their desktop machines for anything useful or incriminating!" the PFY whines petulantly.

"A complete waste of time," I respond, "since I swapped all the good hardware with the shite stuff in the comms-closet PCs to allow us to have a multi-user Quake II challenge from any floor in the building."

"You mean we can't even play Quake on these things?"

"Afraid not. These machines would be lucky to load ANSI graphics, let alone SVGA stuff."

"But..." the PFY pouts.

"No buts, we're going to use our time profitably by getting to know our users once more. We've been far too isolated from them this year - it's time for us to renew our ties!"

All this altruism is making me feel a little queasy, but I gulp down the nausea and continue.

"RIGHT!" I shout. "Synchronise excuse calendars, page 47, Hypotropic Osmotic Leeching."

The PFY's eyes glaze over momentarily as his attention-span safety cut-out trips, but he's back with me in record time.

"I'll just call it H.O.L," he murmurs, blinking rapidly as full consciousness returns.

"Alrighty! Let the games commence!" I cry.

"Games? What games?" the PFY asks.

"You'll find out..."

"I still don't know why the boss didn't veto this," the PFY cries. "I didn't think he'd be stupid enough to go for it."

"He wasn't," I answer cheerily, "but he's been transferred to the Leeds office after a little incident earlier in the week."

"Oh yes?" the PFY asks, curiosity piqued.

"It was tragic."

"REALLY?" the PFY asks, interested.

"It appears that he may have disgraced himself at that Harassment Procedures meeting that the US people made all management types go to."

"The one they imported all those Huggy Feelies from head office for?"

"He didn't say he thought it was a How-To course?"

"No - apparently he had something with him at the meeting that didn't go down well. In fact, that's perhaps the best way to describe it."

"You mean he had a..."

Apparently so. He made some wild claim that someone must've chucked Viagra in his coffee, but I ask you..."

"Weird," the PFY concurs. "Speaking of which, coffee?"

"Yeah, but stay away from the 'instant decaf' till I've had time to dispose of it."

"You complete..."

Our conversation is interrupted by the first call of the day. "Hello, how can I help?" I ask in tones that can only bode goodwill to all comers.

"Hi, my machine keeps losing the time, and my workmate says that it's probably the battery inside the machine!"

"How old is the machine?" I ask.

"Three months."

"Normally batteries don't fail that soon," I respond.

"I think the problem may be that when your machine boots, it sets its time from our network time server, only it's setting the wrong time because your time zone setting isn't GMT."

"Well... >clickety< >clickety< YES! It's set to Winnipeg! Where on earth is Winnipeg?"

"I believe it's in Canada," I respond knowingly.

"Thanks very much!"

"You're welcome!" I respond, then hang up.

The PFY meantime, is gobsmacked.

"What was that?" he cries in disbelief.

"Oh, didn't I tell you? That's the game. Winner takes all - first one to crack has to shout the beers on Friday."

"It's not much of a game. Doesn't sound like much fun!"

"What, and MONOPOLY IS?!"

"Well, no, but it's not that sort of game!"

"I think you're CHICKEN!" I taunt.

"No way!" the PFY shouts. "You're used to it."

"All right, I'll take line 1 as well, giving me twice as many potential callers. Happy now?"

The PFY nods, then grins as Line 1 lights up.

Perhaps I've bitten off a little more than I can chew...

So I'm in a downtown cafe, grabbing a moment's respite (well, a couple of hours, let's be honest) from the maddening crowd - with Mission Control's phone diverted to my unlisted cellphone number, when the phone rings.

"Hello, Networks and Systems," I cry pleasantly, in the manner of one still competing for the 'who can be the nicest to users' competition...

...which I'm certainly not, having won off the PFY by performing a lot of 'space reclamation' on the data servers then leaving sound-byte constructed voicemail messages 'from the PFY' claiming all responsibility and no remorse for doing it. The ill-will towards him at the moment is such that the Boss thought it best he take a little time off.

"Where are you?" the Boss asks, voice muffled by the sounds of traffic from outside my current location.

"In the machine room!" I cry, as indignantly.

"Really? Then what's that noise in the background? I can hear cars!"

"Yes, yes, that's just the Multimedia Demo package that starts every time this new bloody server gets booted," I ad lib. "I'd pull the speakers out but we need them for initial de-bug sounds."

My output bullshitometer is registering three out of 10, so I feel that this excuse will probably suffice for the boss.

"Oh," he responds, confirming my suspicions. "Well I need to get into the computer room as I'm showing some new employees our computing operations. So if you could just pop round and let us in..."

Now call me old-fashioned, but the LAST thing I want is the Holiest of Holies exposed to drooling half-wits with no idea of how or why computers work.

Being a forward-thinking type, I'd planned for the access eventuality by locking out both Mission Control and the Computer Room from all but myself.

"I'm afraid there's some problem with the electronic lock system and I can't seem to get the doors to release," I tell him. "So it seems I'm locked in and you're locked out."

"I see," the Boss murmurs slowly, possibly getting a nasal indication of a rodent in close proximity. "I'll just try the emergency release."

A couple of loud bangs later, the boss picks up the phone, wheezing heavily. "The BLOODY GLASS won't break!" he gasps. "What sort of emergency access is this?"

"I don't know, but it sounds good for security," I mention, knowing that this is bound to get his back up.

"I'm going to call in Building Maintenance to get to the bottom of this - you just hang on in there!" he cries decisively, obviously wanting to make a good impression on all the newbies with his ability to fix difficult situations.

Which means I'm going to have to go back to work after all, as there's only so long that the armoured glass and reverse-threaded access panel screws are going to keep the maintenance guys at bay.

I grab a cab and slip into the building the back way, sneak out the freight elevator and end up behind the Boss and a set of like-minded technical in-breds whose combined IQ wouldn't even make a supermodel's waist measurement.

"Hi!" I blurt, thinking of the PR value of being nice to potential users.

"Where'd you come from?" the Boss asks, gesturing to the buildings bloke that he should keep on drilling now that he's about half an inch into the armoured glass (only another inch to go).

"The computer room!" I cry. "I managed to get the back door open by swiping my card through it repeatedly - probably some read error, or something."

I make a big deal of blowing into the swipe reader, then try my card in the door. It opens, of course, and I surreptitiously reverse the lockout on the doors, then let the crowd into the computer room.

"This is the err..." the Boss starts, noticing that I've come along for the tour, too, and am looking extremely interested in what he's going to say. "Err...tell you what, why don't we let someone from the front line fill you in!"

Suffice to say my presentation was a resounding success - especially after the Boss demonstrated workplace danger by stepping onto one of the floor tiles we leave loosely supported (to stop maintenance contractors from straying) and plunging face first into a machine rack.

On the way out, one of the huggy-feelies from Human Resources meets me and gives me the boss's invite to the 'welcome to the company' drinks that afternoon, seeing how the Boss is probably not going to be able to attend...

And just when you think life can't get any better, the PFY rings to say he knows what happened and that he'll RELUCTANTLY keep his word - a bet's a bet - later that night.

Mental note number two is to swap drinks with him the moment his attention is diverted at the pub - the thought of a laxative overdose doesn't appeal at all.

Out of the kindness of their cold hearts, company management have allowed us contractors to join waged and salaried staff in being eligible (at a reasonably hefty premium, of course) to join the company Health Care Plan.

Sod that. I should get a DISCOUNT for all the work I've put their way. If it wasn't for me, the company wouldn't HAVE a health plan - or at least not one with such a comprehensive Personal Accident Insurance section anyway...

"But it's dirt cheap!" the PFY claims, "and it's got personal accident cover which gives you unlimited time in a private hospital."

"Where no doubt they give you chilli enemas until you manage to discharge yourself," I respond, all too familiar with how good 'good deals' really are.

"No, they've got pictures," he cries, completely taken in by the shiny brochures. "Just look!"

I have to admit the pictures do look impressive, with large stately hospital rooms, battalions of neatly uniformed staff and sumptuous TV-dinner banquets, but I've seen far too many computer brochures to be taken in by advertising.

"It's just advertising bumph," I remind the PFY. "None of it's true."

"It might be," he murmurs.

"It's one of the commandments of computing!" I cry. Never trust the brochure until you've had the covers off!"

"But how can we see what it's like if we don't sign up?"

"Sign up?" the Boss cries, roaring into the room. "You mean the Health Plan? I've been a member for years."

"But what are the hospitals like - have you been to one?"

"Can't say I have," the Boss replies, bending down to pick up the 19-inch flat screen monitor I've indicated is his. "But when I do, you'll be the fir..."

Halfway through his lift, I pop the paper bag that I'd been holding. In shock, the boss shoots to attention a little quicker than he has for a while. "Agh!" he cries, dropping the monitor and clutching his stomach tightly.

Oops.

Of course, the PFY and I take some time off work to see the Boss as he recovers from his hernia op. And do a bit of shopping. OK, and have a few lagers as well. And a ride on the London tour bus - but after that, we went straight there.

At the hospital, we find that my suspicions are unfounded - the place is a state of the art set-up, with remote monitoring that would put our network topology to shame.

We brown-nose an administrative type to get a quick tour of the place, exhibiting a professional interest in their CCPMS (Centralised Comprehensive Patient Monitoring System).

"Basically," the admin-type burbles as we depart the Boss's room, "the system allows all patients to be monitored by a central computer which, in the event of any problem, dispatches a doctor or nurse from a localised aid station."

"I see," I respond. "And what happens if the doctor and nurse are elsewhere playing doctors and nurses?"

After a withering look, the admin-type continues. "The software is aware of staff positions at all times. I assure you that your manager is completely safe from mishaps."

Bugger. We were hoping for a hernia relapse (or five) to get us a couple more office-hours visits to the, er, hospital.

"We have thousands of cables from all over the hospital which terminate in the comms room," a furry-toothed geek from the monitoring room informs us. "The wires deliver all the patient data we need into the master computer and all patient details are available on our touch-screen here."

"Really?" I say, touching the box showing the Boss's name.

"As you can see," the geek continues, "these two windows are camera views of your manager's room, 22b. This box charts his temperature, pulse and respiration, this one his brain wave pattern - all are fed along the 22b cable sets to here, which saves us the tremendous outlay of having to buy individual monitoring units for each... Oh dear!"

The Boss's window has suddenly turned crimson with the words 'CARDIAC CALLOUT'. As the geek and I look on, a team arrives, strips the Boss down and gives him a couple of doses from the kickstart machine.

"Well," the geek adds, mopping his brow "as you can see, the efficiency of our team is second to none."

"Yeah," the PFY says, replacing a screwdriver, "but some of that termination in there is crap. Don't worry, I gave the Boss's cableset a seeing-to and reterminated it..."

The silence, as they say, was deafening. The geek now knows that the Boss got his batteries charged for no good reason, and that given an inquiry, the hospital - and his pet project - wouldn't fare well. He looks at us desperately.

"A tenner a piece should be sufficient for a couple of beers," I say.

"Per day," the PFY adds.

The boss's latest plan is that we're going to put out a news-letter (not electronic - that would be far too progressive and a paper version is much more useful as it can hang around for years, way after the information has passed its 'use by' date) to boost the department's standing...

The theory is that, by publishing a couple of pages of "The latest technology is...", "We've just bought..." and "What you should know about..." on a bi-monthly basis, the workers at the rock face aren't going to notice that we give all the really good kit to management, and palm off the slow and mutilated crap to them. A cover-up in other words...

A brown-nose type from PR is called in to help us create a marketable image, covering all bases from soft-focus photography (the boss does look like his face caught fire and someone tried to put it out with a potato masher) to non-threatening pseudo-computer vocab and pastel-tint papers.

He also excels in choosing topics as far off the issue of service level as possible: how many miles of Cat-5 (high-speed connection cable) there are in the building, how many support staff have been on training courses, the value of our central computing resource, technology we're investigating...And, of course, the boss wants a quick article from me on new kit we're looking at, when we expect it to be installed, and useful user info...in other words, write the whole bloody thing.

Now, I like giving out info to the users almost as much as MPs like talking to their constituents so, obviously, I'm really looking forward to this idea. Not.

What makes it worse is that my directive is to make it so simple that anyone in the building can understand it. I'm just hoping he's not including the security staff in that statement as I don't think our laser printers produce output in crayon.

Nevertheless, with the input of the PFY, we manage to get enough information to fill the required two pages and whip it off to the printers as a rush job, asap - after clearing it with the boss, of course. So I have to admit to being a bit dismayed, even gobsmacked, when the boss bursts into the office the next day in a mood that can only be described as 'fit to burst'.

"What the hell's this?" he asks, waving something ferociously.

"The newsletter," I cry, not to be confused by the obvious.

"I know that, but it's nothing like the one you gave me to proof-read yesterday!"

"No, I had to translate it from the technical jargon you read into something the users would understand."

"But it's a bloody nightmare!" he shouts. "They're confused."

"Well, I have to admit it's possible that the simplification of the text may have caused one or two technical inaccuracies, but the gist of the information is there."

"TECHNICAL INACCURACIES?! You told them the toner cartridges are refilled with ink and that it's relatively simple."

"Well, I didn't think they'd grasp the idea of toner. And it is a simple job of drilling a hole in the cartridge and replacing the toner - if the drum and fuser are OK, of course."

"Yes, well, thanks to that article we've got a printer in the workshop that's only suitable for parts."

"Well, it's hardly a major problem is it?," the PFY chips in. "After all, they've got a projected lifetime of three years."

"That's not the point. Anyway, it wasn't just that article that was a problem - why did you tell people that they should wash their machines out if the network was going slow?"

"What?! Oh, you mean the analogy of a network connection being a pipe and that a bigger pipe lets more go through it?"

"Yes, but you said they should wash their machines out!"

"No , I simply said that, as an owner, you want as much water into your machine as possible, but I was talking about traffic."

"So, why tell them to connect a firehose to their machine?"

"An analogy - big hose, lots of data. Surely no one would've actually connected a..."

"Security will require a whole new set of machines..."

"Oh. Well, it's hardly my fault. You'd think that even they wouldn't do something as blatantly stupid as that..."

"Yes, but what about something NOT as stupid? Why did you tell them to install 'Infector' on their machines?"

"Infector? No, I told them to install 'Detector'. You'd never want to install Infector - that's a virus detector test package, and would screw up all the files in your..."

"Would you like to recover the CEO secretary's hard drive?"

"I'll get the PFY right onto it!," I say, as the boss storms out.

"So, you won't be writing that again then?," the PFY asks.

"Highly unlikely," I chuckle.

"Bugger. I had this really cool idea for letting everyone access your network shares as a distributed storage pool."

"Much too technical; just change it to 'leave your machine unattended and logged in when you go home'. And it's never too late for an addendum..."

"I'll get right on to it!"

Good lad - always willing to go that extra mile for the client.

But that's all fixed now...And, as luck would have it, the unit is cram-packed with old, chunky proprietory hardware clinging to the last vestiges of life by virtue of a shielding layer of dust and fluff that's built up over the ages...But not anymore...

The boss is, of course, the soul of understanding, appreciating the mundane hassle of deleting swags of unnecessary warning email, while applauding the aggressive manner in which I track down and solve outstanding problems.

"If it wasn't really broken, why did you fix it?!" he gasps.

"It's a quality of service issue," I respond, getting the ball rolling nice and early in the conversation...

"What do you mean, quality of service? It was working before, and now it's not!"

"It was only partially working," I sigh, "but it could have packed out completely at any time".

"And now it has!" he cries.

"See what I mean?" I ask, sliding into confusing-logic mode.

"YOU BROKE IT!" he cried.

"Look," I kindly explain, "we get caned by the users for unscheduled downtime don't we?"

"Yes?"

"And we avoid this by scheduling downtimes don't we?"

"Yes?"

"So this is a scheduled maintenance and the users shouldn't be using the systems now, should they?"

"Uh...no?"

"So they don't have anything LEGITIMATE to moan about?"

"I guess not," he answers, sounding just a little unconvinced.

"So, while I'm talking to you, I'm not fixing this kit?"

"Uh...no..."

The boss takes his leave in the kind of casual double-time managers often use to disguise the fact that they've ever been somewhere in the first place. Usually only employed after they've broken something crucial, which brings us back to...

"What's the bloody huge thing there?" the PFY asks, indicating a full-height 20MB hard drive in the bowels of the frame, probably consuming as much power as half the lights in the computer room. You can't blame the lad of course; he's too young to have heard of MFM disks, reel-to-reel tapes or 8in floppies - outside the Reader's Letters section of adult magazines that is...

"That," I say, "is what we used to, in the old days, call a..."

"Hard drive!" the PFY cries, copping a view of the '20MB' written on the side in permanent marker.

"Close, but no banana! It is, in fact" - picking up my trusty rubber panel-beater's hammer - "a service call about to..."

BANG! BANG! BANG! SKEEEEeeeeeeereeerrrrrrrrt!

"...happen."

"And what did that achieve?" the PFY sighs.

"Well, before that unit failed..."

"Before you bashed it with your rubber mallet you mean."

"A mallet that leaves no discernible marks," I add. "Before that, it was a software config and unknown hardware failure."

"And now the engineer will think he broke it."

"After he fixes the hard-drive..."

"Exactly!"

A service call is placed, and in less time that it takes to fly around the world by balloon with a millionaire pilot (including stops), an engineer arrives with kit in hand.

"What - it doesn't come in a sealed bag?" the PFY gasps.

"How do we know it's new?"

"The only thing they get in sealed bags is their bedtime reading," I comment. "Besides, there are probably only three drives like that in the world and they're no doubt fixed manually by Swiss nuns, judging by their non-maintenance price.

The engineer fixes the unit - after returning to the office three times to find a replacement for the failed mystery component that had to be soldered onto the grandmother board - and we chuck it back into service, much to the boss's relief. He's figured out the flaw in my logic, after verifying that my scheduled maintenance message was posted way after I'd broken the kit.

"So, it's all sorted out then?" he asks.

"Yep, back in service and working as per usual."

Satisfied that injustice has been done, he trundles back to his office o figure out a way of referring to this experience as 'good customer relations'. Meanwhile, I return to my desk and am about to start work when a mail message pops into my inbox with the subject of 'System Warning', from the machine of the moment. Sigh...if you're going to do something, do it right. I skip the rubber mallet this time and head for the metal version.

"Back in a minute," I tell the PFY. "Just got some 'alignment' to do." Maintenance really is an ongoing thing...

A tear springs to my eye as he shakes hands with the four Charter members (of which I am one) and prepares to take his oral exam. "Who sponsors this bastard?" the Grand Bastard asks.

"I do."

"And you're satisfied that his thesis High Voltage and its Effect in Reducing Client Calls is an original work?"

"I am."

"Very well." He turns to the PFY. "All that remains now is for you to answer one question from each of the members."

A bit on the formal side, but rules are rules.

The PFY nods wordlessly.

"You've just started a new contract with a firm which pays well, but wants you to document the work you've done - obviously in the hopes of leeching your hard-earned skills. How do you keep the contract and your knowledge secure?"

First, the easy one.

"Ah, I would...claim that I was a devout member of the Church of the Unified Principle of Hermitism, and as such, am not permitted to pass on ideas to others."

"I see...based on the premise that your employer can't discriminate on the grounds of religion?"

"Yes."

"There is such a church?"

"Formed it two weeks ago - a registered charity. I donate all my worldly goods and income to it."

"Very altruistic," the second member comments. "But what about this? You notice that the internal phone directory of your workplace has a full colour picture of the network topology as an appendix. How would you defuse this potential source of cowboy 'plug and pray' by the users?"

"I'd 'upgrade' some terminations to mains voltage and shuffle faceplate labels. Oh, and print an extra fifty copies."

"An extra fifty copies?"

"Yeah, I'd take them to Waterloo and sell them to French tourists as underground maps."

"Excellent," the third member smiles. "Your voicemail queue has overflowed, your helpdesk queue has escalated, and your boss enters your office to find you playing Quake II. What would you do?"

"Err...keep playing so that later I can claim I had post traumatic stress disorder from the game I started at lunch-time - then claim six weeks' compensation for work-induced stress if they threaten to dock my pay..."

"Yes...but I'm looking for a little more than that."

"Oh, you mean use the Application Download server to stick the game on everyone's desktop so I can claim they're all at it?"

"Yes, but I'm really looking for a..."

"OH OF COURSE! Patch the version of the one I download to the Boss's machine to use the Homoerotic-Theme Graphics, and have the game autostart every time his PC's microphone detects a different voice in the office."

"That will do nicely!"

Which just leaves my question. "Your tutor in bastardom has somehow found the wedge of cash you keep inside the supposedly sealed hard drive unit which lies supposedly inconspicuously inside an old AT, underneath your desk."

A sharp intake of breath lets me know that the PFY has just become aware of the practical section of this exam.

"THEORETICALLY, if this were to happen, and the tutor had spent this rather large amount of cash, what would you feel would be the most appropriate course of action?"

"Well, of course we're talking theoretically here," the PFY seethes, "so I suppose I would have to replace it with a similar amount of money from the CO2 extinguisher with the false bottom, which is bolted on to the wall-hook behind the tutor. Oh, did I say is? I meant was."

THE BASTARD!!

"Well," I cry happily, reaching for my briefcase and the electrical 'calibration' device therein. "I'm satisfied that his intentions are genuine, so if there's no objections, I think we should adjourn to the bar to cele..."

The human nervous system sends messages at speeds at several hundred miles per hour. Electricity, on the other hand, travels at about 800 times that speed. Per second.

And yet I still knew what was coming as my thumb touched the strangely rough surface of the keyhole on my briefc...

Later, in the bar, when I'd stopped dribbling and the world had dimmed from about 10,000 candlepower, I bought the PFY a quick drink to celebrate his graduation.

You win some, you lose some.

"Why is that?" he asks, wondering why he's being graced with a private interview.

"Oh, some complaint," I respond.

"Complaint?"

"Yeah, the Linux-geek wannabe from R&D has complained about you."

"Which Linux geek wannabe?"

"You remember - the one you told to link /dev/null to his paging device."

"What happened?"

"Dunno, his machine mysteriously crashed about 10 seconds later..."

"But I didn't..."

"Of course you didn't - I did, but I said I was you."

"Oh."

"But what really surprised me was when you called back in the afternoon to fix his crashing problems, told him his CPU was hot swap-upgradable, and then sent him that replacement processor with a couple of its more vital legs missing. By the time he had got round to putting the old one back in, it was in the same state. Mysteriously..."

"I AM a bastard, aren't I?" the PFY gasps.

"Yes, I couldn't believe it myself," I concur.

"But why would I do such a thing?"

"I don't know," I reply. "It could be that he complained about your, I mean my, shoddy handling of a toner cartridge replacement last week. Or it could be that you were afraid of having to deal with Linux problems all the time. Or it could just be some manifestation of a deep-seated mental upset which you have."

"What mental upset?" asks the PFY.

"Far be it for me to go delving into your psyche, but you could be suffering from some base-level anti-sociopathic tendencies..."

"Sociopathic or anti-sociopathic?"

"Is there a difference?"

"I don't know..."

The discussion of the PFY's need to debase users with higher technical knowledge (and the reasons behind it) are cut off by the ring of the phone...

"Well, here's your chance to find out. That looks like your R&D guy ringing back to find out why ps and a whole other batch of utilities aren't working any more."

"Why's that?"

"Well, I'd be guessing, but I think you might have advised him to unlink his /proc directory."

"But you can't do that?!" refutes the PFY.

"Not with conventional weapons, no. But with that quickly hacked-up program you sent him, it was a piece of cake."

"Oh, but I've got to go see the boss!"

"Yes, I think you should. And I'd take the approach that you're being framed."

"He'll never buy it," whimpers the PFY.

"Oh, I don't know - I think he might, after you put that line in the inetd.conf file, which causes any Telnet to port 187 on his machine to copy junk stdin to the kernel memory..."

"I'm out of control aren't I?"

"You are. You need help!"

"Where am I going to get it?"

"From a specialist. The company has a counsellor for that sort of thing you know."

"Really?"

"Yes, you remember - the one that called us borderline megalomaniac machiavellian types."

"Really?"

"Yes, shortly before you uploaded that virus to her machine under the guise of an email to make an appointment to see her..."

"So, when am I going?!"

"Looks like we both have to go to a group therapy thing tomorrow..."

"Can't wait."

"Ah well, health is health, and an ounce of prevention is worth three hours of holiday..."

"Yes, that's right, put the clippers onto the wire, yes, and snap close." CLICK.

"Did you sort that user's phone out?" the PFY asks.

"I have now. Any more boxes?"

"No, that's the last one. What is all this junk?"

"Oh it's just a load of boxes with lights and beepers in them," I reply. "I'm going to put them in the boss's office."

"This wouldn't happen to be because he wants to increase his hands on?"

"Of course, if he wants to help monitor the network, who am I to stop him."

The boss beams with pride as the PFY and I install the last of the boxes, his rooms is now about to become ablaze with more than 3,000 flashing lights, all with corresponding beeps of various tones. "So this monitoring equipment is usually in the Comms cupboards then?" the boss asks.

"Sure," the PFY replies, screwing in the last LED, which is actually a fibre optic camera so we can see the effects of our experiment.

"Usually we check them for failures every couple of days, but with you on the case, we should be able to really cut down on network problems. It'll look great on the weekly reports."

"It looks very impressive, how do I know when they fail?"

"Oh one of the lights will go out. I'll check in later to make sure it's all running properly," I say as the PFY flicks the ON switch and the room explodes with the cacophony of beeps and the dazzle of lights.

As we leave the office I glance at the PFY. "So, ten quid says he won't last the day."

"You're on!" he replies, sensing quick money. He never learns.

Later in the day the boss's stress levels have obviously increased. He is storming around a lot more than usual and he's barking at everybody, except the PFY, and me. He doesn't want to admit he can't handle the monitoring equipment.

"So how are you getting on?" I ask as I cancel the entire fourth floor's network access, just when the boss is monitoring the equipment to catch it. A quick TCP message to the PFY primes him for a response.

"Oh fine." he replies. "So far I haven't noticed any problems."

Cue PFY. "Uh-oh, the fourth floor's down!" he shouts, furiously hammering irrelevant buttons on his keyboard.

The boss panics as I sigh discreetly. "We need to know what went down, can you go and see what lights went out?" I hand him a network resource chart. "This is a map of all 3,000 lights. Just tick off those which look like they're out," I add helpfully.

The boss is looking very worried now. If he packs in the hands-on scheme the CEO will surely notice and reprimand him for wasting time, so he trots off back to his office as I flick off the power remotely to four of the 3,000 lights and put most of the others on dim.

A few hours later still the PFY and I are standing outside his office as a user has been complaining that his power light is blinking. The result of boss's constant exposure to the monitoring equipment is satisfying to say the least. "WE'VE ALL GOT OUR LIGHTS TO DEAL WITH," he roars. "DOWN HERE I HAVE THOUSANDS OF BLINKING, FLASHING AND BEEPING LIGHTS, THEY BLINK AND FLASH AND BEEP. I CAN'T STAND IT ANYMORE, THE BEEPING AND FLASHING AND BLINKING!"

As the ex-boss is stretchered away, writhing uncomfortably in his straitjacket, the PFY looks penitent. "Perhaps we were a little too hard on him. He was only trying to help."

It's a shame. After all this time, the PFY just doesn't understand that nobody should help a Bastard out in networking. Time for the cattle prod - and a strong laxative coffee later on.

As a result of the PFY's evil machinations he and I are in one of those disgusting huggy-feely sessions where everyone tells everyone else how they feel about their place in the world. Or, in this case, the company. As if it isn't bad enough having to rub shoulders with users, we're supposed to share our thoughts with them.

And of course the tweed-suit who's chairing the session has loaded it with people who the boss feels are victims of the Systems and Networks 'aggressive policy of solving problems'. The theory is that the PFY and I will see the error of our ways when we come face to face with our former 'clients'.

"Now, who would like to start?" Tweedy smiles, looking around the group expectantly...

Ten minutes later, we're back in the office because no one had anything to say. Maybe the PFY's dictaphone put them off - but he only had it because he wanted to reflect upon the users' feelings afterwards...

The boss, noticing our rapid return, forgoes the 'I hope you've learned your lesson' speech. And distressingly, there is still no promise of an Easter bonus.

Being the dedicated type, I decide to put the disappointment out of my mind and do some preventive maintenance on the beancounters' asset audit server machine. After all, they were the ones complaining about our level of service the loudest before the PFY and I walked into the room. (The old sub-miniature microphone in the RJ45 'terminator' trick never fails). Apparently the machine is running slowly.

Our telling them yesterday that they're using twice as many sessions as they'd specced the machine for wasn't seen as constructive criticism.

"Careful with the hammer," the PFY cries, ducking under the backswing of one of my more enthusiastic applications of maintenance.

"Woopsy," I say guiltily, "got a bit carried away there."

"No harm done - to me anyway," he murmurs as he lifts up a floor tile and kicks the results of the 'maintenance' into the subfloor area.

"Takes a licking but keeps on ticking," I say, tapping the battle-scarred machine cage. And, inadvertently, pressing the power-off switch.

Bugger.

In my mind's eye I can already see the chief beancounter hitting the panic button to counter the potential threat to asset security. Not being a believer in coincidence, he's bound to think the outage is a deliberate (which - at least in this case - it isn't) effort to perform some non-audit trailed modifications to the fixed asset inventory.

Sigh.

Like we didn't do that a fortnight ago. During the day. Logged on as him so if the audit trail is ever investigated... However, this isn't going to help much when he sets eyes on the server that looks as though it's done several tours of duty in Beirut.

Sure enough, he's not at all happy when the boss drags him into the computer room to assuage his fears.

"What the hell happened to that?" he gasps, seeing the battle-scarred casing. "It's all bashed about!"

"Well, nothing lasts forever - wear and tear..."

"It's only two months old."

"Two months is a long time in computing," I chip in.

"Besides, it was pretty battered when the courier dropped it off," the PFY adds.

"Why did you sign for it then?"

"Well, it seemed to fire up OK," I said

"Good grief, it looks like it's been beaten with a hammer. Are you sure the couriers did all that?"

"Well, the couriers did some of it, but the cleaning staff probably helped."

"We don't allow cleaners in this room," the boss interjects.

"Yes I know," I say sadly, "That's why I have to do it."

"So you damaged our machine?"

"I'm afraid so," I sigh. "I'm a system administrator, not really a cleaner."

"And I'm a lover, not a fighter," the PFY adds, obviously having tipped a little too much tape-head cleaner on his Weeties this morning.

The humour break is interrupted by the server plummeting to the floor, as the screws holding the shelf in place - loosened during maintenance - lose purchase on the rack.

The aftermath of this little accident doesn't bear thinking about, but, suffice to say, we're in huggy-feely central the next morning, and Tweedy and cohorts are in attendance.

"Now, who would like to start?" Tweedy asks benevolently.

"Ah, I would," I say. "I'd like to share my feelings."

Sigh...

I stumble into work early (well, in time for morning tea) to find one of our boundary routers has crashed overnight, requiring the PFY to be called out to restart it. And, with the boss getting extremely tight on overtime, the PFY has been forced to take time in lieu for the late-night call-out, instead of being paid for it. At least, that's the official version.

The Bastard-interpreted version is that the PFY was out on night alcohol manoeuvres (network people must network), forgot about the Tube times and had to get a cab home - only he'd spent all his pennies in the relentless pursuit of boozing. He would have jumped on the chance to get a work-paid ride back to his humble abode, with time off to heal his battle scars.

Plan 17B from the Big-Bastard Book of Bludges: toggle the power to an important unit, wait an hour, turn the kit back on, then grab a free cab home, with in-lieu recovery time to boot...

Checking the top drawer of the PFY's desk, in case he'd been forced to 'upload some data' during 'call-out', all seems well, so I settle down to read the paper. A few hours later, the PFY stumbles in, looking like his face has been used as a doorknocker.

I eventually get the PFY's story - he was at the local pub doing some late-night 'birdspotting' and followed a 'migration' to an after-hours cocktail drinker. Upset by the Tom Cruise wannabe behind the bar, he'd apparently flicked a lit match onto the spillage of spirits on the bar...not what the big bouncers would call acceptable behaviour. You get that on the big jobs.

So, as expected, he's not feeling great, and wouldn't do our name any good if I sent him out with the Client Unserviceable Equipment list..."Ah, here's that Client Unserviceable Equipment I was talking about yesterday - if you could just visit them and check out what's wrong with their kit?"

What the hell. I'm sure he'll appreciate the chance to counsel a user on the correct approach to the contrast versus brightness dilemma on their monitor...I open a window to the CCTV in the fourth-floor cubicle farm, and crank up the inbuilt microphone to listen to the PFY's first mission...

"So your meetings always get scheduled an hour after everyone else's?"

"Yes. Do you think it's my clock setting?"

"Possibly," the PFY murmurs slowly. "But we should really seek out the root of the problem."

"Maybe it's daylight saving?" the user suggests, helpfully.

"No, that's just a complication. The real cause is most likely to be the inability to find the disk-based Time-Zone configs."

Ah, Find and Disk in the same sentence - he's going for the old F(ind)DISK approach.

"So it wouldn't be the RAM battery on the motherboard?"

"?" utters the PFY, recognising a tinkerer and discarding the FDISK plan.

"You know, that keeps the clock ticking."

"Well, if it were that, your clock setting would reset every time you booted your machine," the PFY points out.

"Oh."

"Mind you, it could be a battery capacitance problem!"

"Battery capacitance?!"

"Yes, you know about Nicad Memory, also called internal resistance?" the PFY says, appealing to the geekal lobe of the user's brain.

"Uh, yes."

"Well, batteries also have a capacitance, storing a reverse charge, which, when a machine is off, reduces the battery voltage, causing a reduced junction voltage in the oscillator controlling time generation."

DUMMY MODE ON!

"Duh-huh."

"So, what do we do?"

"Well, it so happens that I have a booster capacitor kit in the office, which can remove any stray capacitance in the battery..."

Five minutes later..."Isn't that a strobe light with a lead coming from where the lamp should be?"

"Ha ha ha," chuckles the PFY. "No, I admit it looks like that, but that's just a...Capacitance Shield."

"Oh."

"Now, we just connect these leads up like so, plug her in, turn your machine on...stand back...and switch her..."

One small explosion later..."Lucky we found that dodgy nicad!" the PFY gasps. "That could have caused problems."

"But my machine's ruined!"

"No, it's not - look, that processor would make a lovely pendant! And those DIMM cards - they'd be great in a mobile!"

"B...B..."

"No, no, don't thank me - just think yourself lucky we caught it in time! Oh!" he adds, catching sight of a case on the desk. "Does your laptop have the same problem?

"NO!" shouts the hapless user, clutching the machine to his chest.

"Well I'll be off then." Another dissatisfied customer...

So, I'm taking calls because the PFY's on holiday and I have no one to play Quake deathmatches against. It's the usual run-of-the-mill thing with several "power users" from PR ringing to find out why they can't print to the shared laser printer.

Being in a reasonably calm state of mind, I don't expose the callers to the verbal barrage of my thoughts on their inability to read the notices pinned on the noticeboards, stuck to the printer in question and sent via email to them over the past month or so before the printer's retirement from service.

And still they call. Even though the printer has been gone for a week. Even though there's now a person occupying the cubicle where it was.. even though that person tells them that the two-page-per-minute power-sucking monster has gone.

I keep a tight rein on my temper, knowing full well that it really shouldn't bug me that much. My resolve is sorely tested however, when I get a call from the bastard (L)User from Hell. The word incompetent doesn't even begin to describe his technical inability -- he couldn't find his arse with a road map, a compass, mirror and torch. In fact, if his brain activity dipped any lower it would be legal to harvest his organs. And the boss has taken him under his wing in one of his goodwill-generating missions. So far this week he's rung three times because his machine's been hacked (the caps lock key was on when he typed in his password). He also rang to report that his computer had been infected with the "not a system disk, hit F1" virus, and to tell us that our time server was three seconds out from the speaking clock.

Still, the boss is keenly aware of any shortcomings in our service. The phone rings.

"My machine's locked me out again!" he blurts.

"Is your caps lock key on again?" I ask.

"Of course not!" he snaps.

"And what does it say when you get your password wrong?" "I don't get my password wrong! I always write it down on the bottom of my keyboard to be sure!"

"Of course you do," I respond, humbled by the lengths users will go to to protect their work. "And what did the computer tell you when you got your password...er...right?"

"It didn't say anything!"

"I see. And did you check your password this morning?"

"Well, yes! I can't be expected to remember everything!" "And you pulled your keyboard out of the socket in the back of your machine?"

Some fumbling noises follow, after which..."no, I didn't." The bollock-o-meter is registering "Liar, liar! Pants on fire!", so I can guess what's going to come next.

"Oh, it's come right now -- must have been a glitch or something..."

Sigh.

"...But I've noticed that the keyboard plug is a little loose."

Right! That's it! "Yes it's..." I quickly turn to my Excuse of the Day calendar. "...Oh! It's an carbon dioxidation problem."

"What?"

"The oxidation from carbon dioxide in the air makes the plastic shrink. That's why your monitor probably makes creaking noises."

"Oh."

"You can fix it, of course. Do you have a pot plant in your office?"

"Yes, I have a couple."

"Well, chuck one behind your machine and one on the top of the monitor -- they'll extract the carbon dioxide from the air.."

"Of course! Well, thank you for that at least."

"No problem. Now be sure to give them a really good watering so they can generate that oxygen. Lots of water."

Five minutes later the boss is in with the bad news about Mr Incompetent. He survived. And he only lost a monitor and popped a circuit breaker. He couldn't even electrocute himself properly. So now I have to rush a replacement monitor to him.

I get back to my office after installing it to hear the phone ringing. He's upset because the screen colours are up the spout. I almost tell him about the two disk drive magnets I taped to the base of the unit, just to get him to leave me alone, but that's just giving in. And I'm no quitter. It's time to send in a cleaner.

Later on, the boss fills me in on the gory details. "...And, apparently, he tripped and dropped a large bucket of water on top of his machine," the boss burbles. "Which is a hell of a coincidence when you think about it"

"So he'll need another monitor?" I ask.

"Actually no. The cleaning guy was helping to mop up the mess and accidentally slammed Dave's hand in the drawer -- three times!"

"Oh. Well, all's well that ends well. Anyway, can't stop, I'm going for a drink with Mike."

"The cleaning guy?"

Some questions are best left unanswered..