Skip to main content
 

The First Million Words You Write Are Your Worst

18 min read

This is a story about storytelling...

Cray supercomputer

Doing the sane and sensible thing when you're being driven insane is hard. I'm having to think creatively, in order to stick with a job that I hate because it's really easy and really boring, but it pays the bills and it's low stress (if you don't count the boredom that's driving me insane).

I was writing my blog at lunchtimes, to break up the day, but I found that took away the thing that I look forward to doing when I get home in the evening. I also found it frustrating, being at my desk during lunchtime, when people could wander over and distract me. The City is not a relaxing place for those on their lunchbreak. Crumbs on the keyboard is the best you can hope for.

So, I've decided to write short fictional stories once or twice a day, to fill the time. My blog is my therapist, patiently listening and never interrupting, while I pour my heart and soul out. My blog is where I work out all the mixed-up shit that happened in my life. My blog is a non-fiction record of who the hell I am and why I do what I do. My blog sets the record straight.

But, I need a creative outlet. Writing my blog is kinda creative, but there are certain needs that have to be met. If something is bugging me, or coming to the surface from my subconscious and memory banks, I've gotta get it out, I've got to put it into words and start to make sense of everything. Writing creatively is different. Writing creatively is scratching that itch that I never get to scratch, as a software developer or leader of software development teams. Software is a science at the end of the day, and for sure it's a black art, but it's important that I don't rely on my job for everything that I need.

And so, today, I wrote the first fiction that I have done in my adult life. I don't know why I've shied away from it. Perhaps it's because I had seen it as childish, juvenile. Perhaps it's because I was afraid that people would laugh. Perhaps it's because even I would laugh, when I read it back again in future. So, it seems sensible that I would hide behind humour, satire. It seems sensible that I would use elements of fantasy, rather than trying to write anything serious, earnest.

I don't do role play. I don't play Dungeons & Dragons. I don't do any kind of fantasy at all, and wearing the corporate mask the whole time is very draining. It's important to not take yourself too seriously sometimes. Wear fancy dress. Pretend to be somebody, something you're not, just so long as it's for fun. I don't really do fun. My life is very simple: work, sleep, eat, repeat... plus some blogging.

I'm not going to publish every one of my stories. In fact, until I know what to do with them, I'm unlikely to publish any of them. I'm going to publish the first one I wrote, in the vague hope that anybody's reading and might have some feedback, but until I find my particular sweet spot, I'm going to keep things mostly under wraps.

Anyhoo, if you've persevered reading this far, I shall cut to the chase and introduce the first short story I ever wrote in my adult life.

It's called The Sysadmin:

The users were scared.

 

The office expanded almost as far as the eye could see, with row upon row of birch veneer desks, in two large columns. The room was cleaved in half by a walkway running down the middle. The polystyrene ceiling tiles were dirty and many of them were broken. Fluorescent lighting bathed the room with a dim yellowish flickering illumination, which harshly lit the people and furnishings, whilst somehow not being bright enough to bring out the colour or definition of anything.

 

Identical swivel office chairs each had their own character, through the damage they had sustained. Some had broken backrests, some were missing armrests, some had their once colourful fabric, hanging frayed from the edges of the jagged black plastic that was designed to conceal stained foam and how cheaply made these pieces of furniture were. Each chair had indecipherable markings that identified it to its owner. Some had initials scratched into the plastic of the backrest using a sharp implement. Some had letters or symbols daubed onto them using Tipp-Ex correction fluid. Some had rectangular sticky labels that were half ripped off, with a name now longer legible, written in felt-tip pen.

 

The grey carpet was almost uniformly patterned with brown patches from spilled instant coffee, which had become so trodden into the floor covering that they were almost unnoticeable in the context of the shabby decay of the office. There was a stripe that was slightly browner, running down the walkway in-between the two columns of desks, that led to the coffee vending machine, water cooler, and a door marked “NO UNAUTHORISED ACCESS”.

 

Clearly unnerved, but silently huddling together in the walkway and all looking towards the man who had just entered the office, the users were no longer at their desks. The users now stood wide-eyed, clustered in front of the man, but unsure what to say or do.

 

“Hi, I’m the system administrator” the man began. “Did somebody phone IT support?” he asked, addressing the group as a whole, unsure of who to direct his question towards.

 

The users mumbled to themselves almost inaudibly, but didn’t seem to be communicating with each other or the system administrator. They were nervous. Nobody wanted to speak up. Everybody knew, but nobody wanted to say.

 

The users mostly looked the same, men and women, despite subtle differences in appearance. The women wore flowery blouses in muted pastel shades, sensible flat shoes and rimless glasses. Their wavy hair was tamed by hair clips and cut to a uniform length somewhere above shoulder high. They were all overweight and with slightly reddish cheeks. They looked flustered.

 

One of the users spoke up. It was a man. You could tell he was a man, because he wore an off-white button-down shirt with a blue biro in the front pocket, like all the men. His shirt was wrinkled and half-untucked from his bulging waistline. His neck crumpled the soft collar, so that his head and body were just one bulging mass. There were coffee stains down his front and he had clearly wiped his hands on his trousers many times after eating. The hem of his stained trousers didn’t reach the top of his black scuffed shoes, and his white socks were showing.

 

“It.. it.. it’s the… the...” he stutteringly began.

 

The user looked around, with slightly wild eyes. He was desperately hoping that one of the other users would now speak up, but they all looked away and avoided his eye contact. Somehow, a gap had formed in the group around him, as if everyone had stepped away from him without anybody noticing. The user seemed to be attracting all of the inadequate light in the room. It was as if a spotlight had picked him out, and he now stood, floundering, all on his own.

 

“I.. I… I… I’m not in charge here” he continued.

 

“It’s OK, just tell me what’s going on.” said the system administrator.

 

“I didn’t do it. It’s not my fault. We were all here, just getting on with our work” he started to protest.

 

“Don’t worry, I’m not here to blame anybody. Just tell me what the problem is” the system administrator offered, as kindly as he could, putting on his most understanding and approachable face. “You can tell me” he said.

 

“It’s the… it’s the…” the user haltingly continued, struggling to get a handle on his rising sense of panic, almost choking. He felt a sense of responsibility that he was totally unused to.

 

“Please just tell me what the issue is. Somebody logged a call with IT support” the system administrator pleaded, now losing his patience.

 

“It’s the MAINFRAME” the user blurted out. There was a sharp intake of breath from all the other users, as the man spat out the final word, even though they all knew.

 

The system administrator rolled his eyes. “Really? What’s wrong with the mainframe?” he asked, as if a practical joke was being played on him. His face now betrayed a deep skepticism and the impression that his precious time was being wasted by a bunch of low-brow imbeciles.

 

“It’s angry” the user said. “Yes, it’s angry” many other users now quietly agreed, in defence of their colleague. “Angry” and “it got angry” they all muttered, not really addressing anybody except the room they were all stood in.

 

“Right, get back to your desks. I’ll take a look” the system administrator said. He stepped forward, having to push people out of the way, as clearly nobody was in any mood to return to their desks. The users were stood in a trance-like state, just muttering “angry” below their breath, and staring at the system administrator as he tried to pick his way through the crowd and make his way down the walkway in-between the two columns of desks, where all the users were still clustered.

 

Walking through the office, up to the door marked “NO UNAUTHORISED ACCESS” the system administrator glanced back towards the group of users, who were still crowded together on the opposite side of the room, near the exit. They were all looking at him, in perfect silence and stillness.

 

Reaching for the door handle, the system administrator was about to twist it and enter the restricted area behind, but he hesitated, and instead put his ear to the door. It sounded like… footsteps. But these were not the footsteps of your average light-footed person. It sounded like deep thuds of metal and rubber on concrete. DUSH! DUSH! DUSH! Would come the thumps of heavy machinery hitting a solid floor in a slow rhythm, and then stop, and then repeat again.

 

In a moment of calm rational thought, the system administrator decided that perhaps one of the air conditioning units had failed, and the motors that drove it were now causing some kind of mechanical fault to create this racket. Immediately, he twisted the door handle and opened the door a fraction.

 

Inside the restricted area, it was dark. Almost pitch black. This was unusual. The restricted area should have been well lit.

 

The system administrator craned his head through the doorway. It looked as if the glass doors that allowed entry into the temperature controlled housing for the mainframe, were open. The doors should not have been open. The vibration absorbing shock mounts, that the mainframe sat on top of, were in the housing, but the mainframe was nowhere to be seen in the darkened room. The system administrator couldn’t see the whole room because he was just peeking in through the gap in the doorway. The thumping had stopped, and everything seemed eerily quiet. Where was the hum of the cooling fans and the chatter of the hard disk drives? Where was the bleep and crackle of the networking devices? Where were the blinking LED lights that signified the activity of the mainframe? It seemed like the restricted area was empty and lifeless.

 

Then, a gigantic shape lunged out of the darkness. A humongous black box, big enough to fill a quarter of the room, suddenly thumped forward out of the corner, where it had been previously unseen due to the poor lighting. DUSH! came an earsplitting sound, as metal crunched into the reinforced concrete floor. A sudden scattering of red lights lit up across the front of the object as it thrust towards the door where the system administrator stood.

 

Quick as a flash, the system administrator slammed the door shut and ran down the walkway in-between the desks. Almost scattering the statue-like users who were still milling around near the exit, he left the office. Just before the office exit door slammed shut behind him, the users heard him call back to them: “I think it’s hungry”.

 

The users appeared to wake up, and now a mild kind of panic spread amongst them. They started to talk amongst themselves, while also shooting nervous glances towards the door to the restricted area.

 

“Should we get out of here?” and “it’s dangerous, I don’t want to be in here when that thing escapes” they said to each other, in hushed tones. The users were quite calm in their indecisiveness. They mumbled to each other in low voices for several minutes, with no clear plan of action emerging.

 

Then, the system administrator threw open the office door again. He struggled, getting stuck in the doorway. In his arms were bundles of grey cables, like a great mass of tangled rope. The users cleared the gangway for him, but nobody stepped in to help him. Finally overcoming the obstruction, the system administrator burst through the doorway, and made his way to the restricted area door, while tripping up and dropping cables along the way. He dumped the tangled mess next to the “NO UNAUTHORISED ACCESS” door, and then made several trips back up and down the walkway, picking up the cables he had dropped and adding them to the pile.

 

Grabbing handfuls of cables, and massaging them into a giant knot, the system administrator now took hold of the door handle in one hand, while holding the beach-ball sized lump under his other arm. With a single fluid motion, he flung open the door to the restricted area and threw the cables into the room.

 

The mainframe roared with a bloodcurdling mixture of computer fans that were spinning at maximum revolutions, hard disks that were clattering, network devices that were chattering and the screeching sound of the twisted metal of its frame. The front of the mainframe was an angry mess of red LED lights, that flashed furiously in the darkness. It lunged for the door, but the system administrator was too quick and slammed it shut, before diving to one side with his back flat against the wall, panting heavily.

 

There then followed a graunching, crunching, high-pitched sound of plastic being stripped, broken, and metal being bent and torn, and then the low hum of fans and hard disks spinning. There were a few thuds and crashes, as the mainframe stomped around, and then things went quiet again.

 

The system administrator repeated the procedure, of rolling up balls of cables and tossing them into the restricted area several times, before the pile was exhausted. The users watched nervously from the other end of the office the whole time, although they craned their necks in interest, trying to see what was going on.

 

There was a moment of calm when the pile was gone. The system administrator and the users momentarily relaxed. Perhaps the mainframe was satisfied?

 

Then, a roaring and stomping started, many times worse than it had been before. The speed of the steps was rapid, and it sounded like the mainframe was tearing the room apart.

 

The system administrator looked worried, then pensive, and then he appeared to have a eureka moment. He sprinted energetically towards the office exit, hardly breaking his stride as he flung the door open and disappeared. Just as the door was closing, he called back to the users: “I think it wants dessert”.

 

Some time went by, and the users were getting very nervous, as the mainframe set about destroying the restricted area. Several times, the door seemed to vibrate and rattle in its hinges, as if it was going to be blown wide open at any moment. The users started to back up against the opposite wall, trying to get as far away as possible, but still unwilling to leave the office.

 

At last, the system administrator returned. He strode into the office carrying a brown cardboard box of modest size. He walked down the walkway, looking back at the terrified users with a cheeky grin. With a twinkle in his eye he produced a flat object, about 4 inches square, from the cardboard box. “I think it’ll like these” he said.

 

The system administrator proceeded to slide floppy disks through the gap at the bottom of the door to the restricted area. The floppy disks came in various sizes. The bulk of them were 3 and a half inches, with a metal sliding part that protected the black plastic magnetic disk inside. A lot of them were 5 and a quarter inches, and had no metal protective part. The mainframe gave a grunt of approval each time that it was fed a disk, but its satisfaction was audibly less pronounced each time.

 

However, the system administrator had saved the best until last. Producing some 8 inch and 3 inch floppy disks from smaller white cardboard boxes that had been concealed in the bigger brown cardboard box, he now fed the mainframe these rare delicacies. It didn’t take many before the mainframe started to sound positively delighted, with a crescendo of modulated digital signals gracing everybody’s ears.

 

The system administrator disappeared into the restricted area, opening and closing the door quickly behind himself. Soon, soothing noises and words of encouragement could be just heard outside the room, and there were a few thud-like stomps, and then the sound of computer fans and hard disks whirring back into life. As he stepped out of the restricted area, the lights in the room were back on, the doors to the glass housing were closed and the mainframe was back on its anti-vibration mounting. The LED lights on the front of the machine flickered in ordered patterns, and a thick trunk of network cables that hung from the ceiling had all been plugged back into the gigantic black box.

 

As the “NO UNAUTHORISED ACCESS” door closed behind the system administrator, hundreds of terminals blinked into life on the desks of the users. The office was now bathed in light from the computer screens that were displaying lines and lines of green text on a black background. The green glow seemed to soothe the nerve-jangled users, and they all went “aaahhh!” in unison, and started to slowly file back to their desks without prompting.

 

The system administrator ambled up the walkway for the last time that day. Most users were now seated back at their terminals, busily performing calculations for the mainframe, happy again. He paused at the office exit and looked back over a sea of green screens, with users hunched over their beige plastic keyboards. The natural order of things had been restored.

The end etc. etc.

Anyway, I noticed that my story was 2,500 words, which is about 3 and a half times more than what I normally write. If I write two stories like that every day, plus my blog, I'll be producing over 4 novels a month. That's NaNoWriMo (National Novel Writing Month) on steroids. I think I'll burn out.

So, it remains to be seen what the sweet spot is for the length of the stories, and what I'm going to write about. Maybe I will be struck by the infamous writer's block. Maybe my enthusiasm for the whole endeavour will fizzle. Maybe I will never find anything that I think people will enjoy reading.

Let the games commence.

 

Tags: