• (cs)

    Anyone want to summarise for those who come here for the WTF rather than the Lovecraft pastiche?

    PS Alex, having background-color and color both black makes it quite hard to read comments...

  • Merus (unregistered)

    The WTF wasn't much, but the Lovecraft pastiche was quite enjoyable.

  • Anon anon (unregistered)


  • (cs)

    For those whose eyes hurt as much as mine: From the archived blog of Paul, recovered from a USB stick found beneath the raised tiles of a decommissioned server room, long forgotten.

    The most merciful thing in the world, I think, is the inability of the human mind to correlate all its contents. But what of these modern times of connectivity, with the ease of the piecing together of disassociated knowledge? Can any information be safely sequestered away-- fragmented and separated, never to come together and burrow in the minds of men?

    My knowledge of such things began in the time of yore, almost time immemorial, during my tenor at Initech. It is where I discovered the madness that lurks in my mind, my soul, my dreams, even to this day. A madness I pray can be excised with this blog, that through writing these words I may achieve some form of catharsis and perhaps, at last, peace.

    I. The Horror in ASCII

    I was once a technician at Initech, at first a lowly one, but then increasingly senior as the company saw greater and greater success. The company grew larger, its tendrils hungry to feed off more. It drew in more resources. More people, each more diverse than the last, in both personality and physical location. Entire companies were joined to Initech by way of merger and acquisition. Initech's infrastructure grew in lockstep. Servers were purchased. Remote locations came online. And then the catalyst of this fateful tale; an alliance with IBM.

    In an amount of time far swifter than a humble technician like me was ever used to, a wave of blue change swept through Initech. The details are boring and beneath us both, dear reader. But sufficient to say, everything became IBM. Initiech's ERP was changed, and it now ran on AIX, the blue giant's own flavor of UNIX.

    With the changes done, Initech turned its new infrastructure and capabilities on Minitech, a large competitor, and swooped upon it to perform the inevitable and unavoidable acquisition.

    But while the leaders and scholars of Initech were looking out, technicians such as I were looking in.

    In those tumultuous days, with so many of our people being remote, but all our resource being centralized, remote consoles were the only way to bring both together. Employees connected to the ERP software via telenet, using the Korn shell. Occasionally-- well, far more often than that word would imply-- something would go haywire with the dial-up connection. The modem would misbehave, the phone line would be too noisy, or perhaps just fate would intervene in its mysterious ways. The connection would be assaulted with electrical noise, spraying the current working directory with an acidic wash of random ASCII. By methods and designs beyond my kin, those maelstroms of incomprehensibility would wander too close to a cat command, or end up on the wrong side of a pipe. Those unfortunate directories would be overwhelmed with bizarre files with unpronounceable names. The resultant directory listings would be littered with these mangled corpses of false files, a visual mess beyond visual understanding.

    It was on the eve of the acquisition of Minitech when I looked too far inwards with only the best of intentions. But intentions are only as good as their execution. Results of actions are the reality of the world, as are all the consequences wrought by them.

    I, with my aforementioned intentions, wanted to welcome our new Minitech brethren with a system that was not littered with these abominations that lay foul to our ERP. These malformed files had always been a horror I tried to see only in my periphery. Something I acknowledged existed, but did everything in my conscious power to avoid interactions with. But I was interacting with the system during the merging, and these things were ubiquitous. Pieces of madness, strewn about. Little things, like motes in the corner of your eye. Tiny, unnoticed. Until they're notice. Then you cannot unsee them. I was driven.

    But I did not know how to exercise these devils. How can you drive away that which you cannot even address directly?

    So in my thrice-damned cleverness, I devised a workaround. One that could only be borne somewhere on the continuum of youthful bravado, and outright insanity. Before this incident, I could excuse my behavior as the former. Afterwards, I can only dare to hope to escape from the latter which I know pulls at my hindbrain even to this day.

    I could not refer to those modem-noise files directly by name. But, oh wonders of scripting, I could enumerate the extant of respectably-named files in a directory. With arrogant keystrokes, I created a script that create a temporary folder elsewhere, tuck away all the proper files into the encompassing safety of its embrace-- and then in a single fell swoop, banish the malformed miscreants into the ether with a single rm * command.

    I ran my precious, foolish script on a directory or two, and it worked a wonder. The directories at long last were pure and clean, swept free like a warm, sweet wind lifting the heavy lung-scalding smog from a valley. It worked well and I congratulated myself. But-- oh, huberis, the folly of man-- I knew cleaning a few personal directories would not be enough. There was an entire filesystem that, over the many epochs of times, had been defiled upon by the foulness.

    It was everywhere, and at last I could fix it. I unleashed my script like the furious right hand of the archangels themselves. Directory after directory, expunged. And it worked perfectly everywhere.

    Everywhere, that is, until I discovered modem-noise files in the root directory.

    In a hazy stupor, like being drunk on the power I wielded, I turned my script on the root directory, and unleashed. It would be simple enough, just like every other cleansing thusfar. Move the good stuff into a temporary folder. Remove the noise. Move the good stuff back.

    I never made it past the first step. Perhaps a small part of my brain realized only after the command had been executed what the connotations of what I'd done were. Surely, dear reader, as an experienced Unix system admin, you can feel the horror that only dawn on me like a rising tide. My terminal froze, locked up with a sudden, bone-jarring stop.

    A chilling realization emerged in me, and become clearer with each flash of the pulsating, yet now lifeless, cursor.

    The server must have been using those files.

    In the glow of only the infernal, useless terminal, and the midnight moon streaming into the office-- I nearly wept.

    That this could happen was impossible! It must have been a simple glitch; not unlike those line hiccups that had caused these demon files in the first place. But my terminal did not reboot. I flipped the reset switch. Once. Twice to be sure. And then with a violent outburst, thrice and be damned to hell you infernal server! I was overcome with near mortal anguish, the visions of thousands of users lost adrift, disconnected for eternity, all caused by me. Surely there were backups. Someone could undo this conflagration. Someone could fix it for me right away, first thing in the morning, and be a conquering and well rewarded hero.

    But no. None of my fevered ramblings would come to pass. The server was dead, killed by my own folly.

    There was naught to be done but travel back to my residence, and spent the night in the sleepless fits that a man wrought with guilt should suffer. And suffer I did. Never had six hours stretched themselves into an eternity with no horizon before my eyes.

    II. The Tale of Marie, System Controller

    Without knowing the warm comfort of sleep, I returned to the office at a time early enough to know that I'd be the first one in. A shamble of a man, lumbering back to the scene of his horrors. I should be at the front door, personally meeting the face of each employee whose day I had destroyed. Would I greet them apologetic, a meek smile on my face to mask my dread? Prostate myself on the sidewalk before them, the concrete as cracked and trod upon as I felt?

    A small blessing in disguise awaited me in the breakroom. Marie, the project manager and system controller, was by the coffee machine, slowly savoring her morning libation. It meant she hadn't yet discovered the fatal deviation I had thrust upon the server. If she had, she would not be enjoying herself as such. A small blessing indeed, for it meant I could brace her.

    But I couldn't brace her enough. It was only by the grace of god that she had finished her coffee, so there was nothing left to spill. Without a word, we marched into her office.

    She tried to log into the machine from her terminal, a vain attempt for sure, but I could not blame her for wanting to verify my folly herself. It was something almost beyond comprehension. It could only be experienced.

    Marie was silent for a moment. Each time her nostrils flared, or her lips parted for breath, I recoiled, knowing a viscous but well deserved berating will burst forth from her. But bless her for being a rock of professionalism amongst the insanity swirling around this situation, for it never came. Instead she opened a drawer that has not been opened in time immemorial, and retrieved a key unlike any I had ever seen. It was oddly shaped; curved around the head but not round; tiny spikes and spokes protruded from it at odd angles. Even though the key was ancient, it was not tarnished. In fact it looked as new as the day it emerged from its forge, it's chrome plating unscathed by use.

    "It's a key to the server itself," Marie told me. "Only to be used in the direst of emergencies. A key to the maintenance shell of the server."

    Together, we travelled to the server room. We passed the steady stream of arriving employees-- their faces an even mix of blessed innocence, having not approached their terminals yet; and confused, lost and angry from those who had. We went through a door I'd never been though, and down a flight of stairs I barely knew existed. The temperature had noticeably dropped. In the dimly lit concrete hallway that ran the length of the building, but far underneath it, I could almost see my breath escaping from my mouth like a vagrant soul trying to rend its way from this place.

    "This leads to the server room," she told me. Which was odd, because I thought the servers were housed upstairs in the tech room. But no, for I was mistaken.

    This was the server room specified and equipped by IBM. This was the AIX server room. It was where the ERP itself resided. Separate from the email servers, from the webservers-- from all of the infrastructure I had ever physically touched. This was beyond what I, as a lowly technician, had ever known or dreamed of.

    And then we passed beyond a steel door that might once have been red, and entered the server room. Racks I did not recognize. Boxes that looked like nothing I had ever laid eyes upon. Reams of wiring dipped and swooped, to and fro, in and out from places obscured by shadow. None of them were the same. RJ45. Ethernet. Was that a token ring terminator? How ancient were these connections? They seemed to twirl in both directions at once, and skew away at angles that simply did not look right. The geometry of the cable runs was abnormal.

    And beyond all this bewildering whorl of technology, a single box sat on a desk like a steel dais, enclosed with a cage of criss-crossed metal to keep the box safe. Or perhaps to keep people safe from the box.

    Marie unlatched the cage and parted its double doors slowly, opening them like some unholy ark. The hinges cried out in protest, an unearthly screech extenuated by the deathly silence that was pervasive in the room. No, I suddenly realized-- not silence. A constant and perpetual hum. A single tone at a frequency that would not stay still. An eternal white noise that lurked acoustically in the air. A sound I hadn't noticed, but now couldn't get out of my ears.

    Marie inserted the strange key into a receptacle-- a black hole on a black surface in a dark room. It shouldn't be possible to see it. But the key nestled into place. She turned it, and a new sound filled the air. A high pitched sound, and it was rising. Something coming to life, if life is how you would dare to describe it-- this shambling thing that was merely a hollow shell of what it once was.

    The built in monitor glowed. The server pulled a maintenance shell from beyond comprehension, from beyond userspace, and projected it onto the screen. Marie laid her fingers on the keyboard.

    It was a direct connection to the soul of the entire system.

    "Will this work?" I dared to ask her.

    "I hope so," she said quietly, her fingertips twitching, "Or else I'll have to call..."

    Her voice trailed off.

    She typed a command, and the system told her it couldn't be found.

    "That-- that cannot be," Marie said, staring at the incomprehensible and impossible error message. That command she'd typed shouldn't be missing. It was a standard command, known by all, repeated by all, in the kernel since the earliest recorded epoch. Maybe even before. It was part of the system.

    The system I had sliced into pieces and scattered. Oh.

    I spoke of the temporary directory. "Look there for the commands."

    "I can't," she replied, "ls is not found."

    The sun didn't rise today. The trees have no trunks. Water itself is not wet. To utter any such phrase would have been equal in absurdity to what had just passed Marie's lips.

    It can't simply be gone. The ls command must exist. Unless-- no, I couldn't think of it. I refused to acknowledge the thought that gnawed at me. To think of what I'd done. To think of why I'd done it. How I'd done it.

    I couldn't address those modem files directly-- only indirectly by inference. Why could it not be that way again?

    "Does cp exist?" I asked.

    She typed so slowly, fearfully. Tap. Tap. Thunk.

    Silence, and then: "Yes."

    A single word, but a rush of hope beyond comprehension. As deep as we were in the mouth of madness, a single, solitary word of hope had been uttered, and it was louder than any cacophony of cooling fans.

    "We can do this," I said at last, "The commands aren't missing. They just are relocated beyond the veil of the normal directory structure. But I know where they are. In limbo. But we can pluck them back, put them where they belong. Try system commands, one at a time, and if they fail-- we can restore them one at a time with cp."

    "I hope so," Marie said again, and typed. The first command copied. Then the second. And a third.

    One by one, we identified the commands, pulled them from the temporary void, and restored them. After an hour, we had pulled the server back from the brink of death, and restored a functional operating system. Barely functional. Perhaps I should only describe it as, at best, stabilized. The commands worked, but not as expected. Interactions were off. Permissions were not correct.

    And that sliver of hope, just like that, was extinguished under a burden of realization. We had restored the command structure of the server. But there were still files in the void of the temporary directory. And unknown portion of the server was still sequestered away, and the maintenance shell simply could not put them back into place properly. Even if either of us knew how.

    "It's over," I said, defeated. But for some reason, Marie wasn't.

    "No, it isn't," she said, a wicked grin on her manic face. How could she be pleased? Had the overwhelming burden of what I had befallen upon us broken her at last? "The server's operational again. If you hadn't helped me restore that little bit, then they would have just come in and destroyed it, replaced it wholesale-- along with anything we'd customized or that hadn't been backed up. The entire merger would have been lost. But now-- they can work with this. I know they can."

    "They?" I said, confused as Marie pushed past me, striding like a maniac towards a desk in the corner. "Who are they?"

    She picked up a dusty wired phone, and phoned the number pasted on the wall. She turned and finally answered me. "IBM Support."

    III. The Madness From The Blue

    She spoke into the phone, at first in English, but then slowly slipping into tongues I did not comprehend. Acronyms. Chains of words that should be familiar but lost their meaning when put in the order she did. I could not understand Marie, but I could read her body language. Apprehensive and pensive hope.

    I wish I could share any of those feelings, but this place and its strangeness was getting to me. Blinking lights. Dark shadows. Machines that may or may not be doing their job.

    The central heart and soul of it all limping along the fine line between life and death.

    But we had to wait there for those she had summoned. We barely spoke at all. What did we have to talk about? What did we dare say aloud in this place?

    Soon enough, thank any deity who would hear me, they arrived. Men in gray suits, decorated with Initech's very-ist of Very Important Person visitor tags-- and IBM identification cards. The ancient handlers arrived, those who brought their tomes and their incantations and rituals. And their price. It would be steep, and non-negotiable.

    Marie agreed to it.

    They set up around the server, briefcases full of keys like Marie's but stranger. Wires with ends like gaping maws of no shape I had ever seen. Terminals that were like Initech's own, but only on the surface. And before they began, they shooed us out of the server room, like a cult that held onto their secrets tight against the threat of public revelation.

    I did not wait for them to ask twice before fleeing that place. Past the not-red door, back up the concrete hallway, up the stairwell, past the hordes of displaced workers, and finally out into the sunlight.

    I do not know what on in that basement, and for the sake of whatever sanity I have left to this day, do not want to know. File systems got mounted. Network connections were massaged back together and brought online. The system was dragged back from the brink, piece by piece, into a patchwork. By the end of the day, terminals flared back to some imitation of life.

    I never saw the strange men from IBM leave, but by the time I dared to go back into the office, they were gone.

    The server was up once again, accepting terminal connections. It reached out to the world, and let the world reach into it. It was a server once more. All of its myriad pieces had been stitched back together, the chaos of its file system oozed back into place. On the surface, the system looked normal. But I had seen into the deep. Even now, I could see the patchwork. The scars. The artifacts of what had risen. System files with creation dates far too new. Permissions for critical files that weren't set right. Customizations that had simply vanished into the abyss.

    Whatever had been done to it was unnatural and just a kind layer of "good enough" overtop a horrific layer of madness and wrongness that went all the way down to its kernel. A constant reminder of that it had once been an empty shell of a system, barely alive-- a portal straight into chaos.

    Though the system ostensibly worked, eternal and irrevocable evidence of the madness remained. I could never be confident that some random glitch was not related to the great awakening of chaos, and the desperate efforts of the silent few who put it back to its slumber.

    Initech moved on from the incident, and brought Minitech into the fold, and several other companies since. Management always talks of replacing the ERP system, and the AIX server that hosts it. The first few times such a decision was raised, so too were my hopes. My hope that the shambling patchwork beast in the basement could be decommissioned forever-- scrubbed from thought and memory. But that project, like all corporate projects, was always six months away from completion. So while a switchover may occur one day, for now the server was just let to be.

    No one delved into details of the incident. Management had a vague idea that something had required a high-level support call. Technicians knew they needed to let well enough be and not touch the patchwork server. One by one they vanished from the company, always with an excuse. One by one they were replaced with new technicians, fresh of mind-- until all what remained was ancestral, institutional knowledge that this thing was touched by evil. That trouble and danger surrounded it. DO NOT TOUCH, though to their blessed sanity, they never knew why.

    Even Marie took the knowledge of the madness with her when she left Initech shortly thereafter. She had given strange thought to properly documenting the incident in extreme detail, and had even started to do so. But she thought better of it and stopped, and she would have destroyed her ticket database had LinkedIn not so suddenly seized her.

    And thus no single person had complete knowledge of what had happened, nor the means to piece it together. No one knew the full extent of what transpired that fateful and horrible day, or the true nature of the shadow hulk of a server that the day produced.

    No one, but for myself. I have gathered together all evidence and documents I could find of the incident. The flood of ticket requests from the day. Work orders from the IBM cultists who faced down The Thing. Marie's incomplete post mortem. The seemingly random spattering of bug reports that trickle in even to this day. All on this USB stick. With it shall go this blog of mine-- this test of my own sanity, wherein is pieced together that which I hope may never be pieced together again. I have looked upon all that the ERP has to hold of horror, and even the satisfaction of system administration and the acquisition and adaptation of new technology must ever afterward be poison to me. But I do not think my tenure at Initech will be long. As Marie went, as so many poor technicians went, so I shall go.

    Let me pray that, if this blog outlasts me, my web administrators may put caution before audacity and see that it meets no other webserver.

    I know too much, and still-- in its cage at the Server Room, the patchwork ERP waits dreaming.

  • (cs)

    Undramatized version: Idiot moved /bin, server broke. Shell had own version of cp, used that to fix shit. Then called support to clean up the remaining mess.

  • Nick (unregistered)

    What the fuck I ain't reading this shit, it's burning my eyes.

  • Honnza (unregistered)

    TRWTF are invisible comments. Or is it better that way? I'm not sure. Also, the fact that the addComment font has a non-halloween stylesheet is a WTF.

    captcha: vereor - the meteor of truth. It will come crashing from the skies, its remains will bathe the athmosphere for six days, and no-one will be able to lie during those days. Brace yourself, lawyers.

  • (cs)


    bad modem didn't filter out scrambled data resulting in bogus files with untypeable filenames

    employee created script that moves valid files to tmp and removes all and restored from tmp

    script didn't ignore directories

    employee let it loose on / and removed /bin ****ing the server

    he should be glad "bin" is before "tmp" otherwise it would have required a restore from backup

  • Oslo (unregistered)

    document.getElementById('MainContent').setAttribute('style', 'background-color:white!important')

    document.getElementsByClassName('ArticleBody')[0].setAttribute('style', 'color:black!important')

  • Oslo (unregistered) in reply to Oslo
    document.getElementById('MainContent').setAttribute('style', 'background-color:white!important')

    document.getElementsByClassName('ArticleBody')[0].setAttribute('style', 'color:black!important')

    But then again, if you made it this far you probably figured it out by yourself.

  • Pavv (unregistered)

    Seriously? This is crap. That guy^^ just summarized a 4000 word article in 25 words - and nothing was lost. Can anyone recommend a site that's like what DailyWTF used to be (ie not crap)?

  • Aris (unregistered)

    Apparently testing the new CSS before moving in production is too hard for a website named "the daily WTF".

    And TL;DR

  • r0b0 (unregistered) in reply to Oslo

    Or just press Ctrl+A

  • (cs) in reply to Aris
    Apparently testing the new CSS before moving in production is too hard for a website named "the daily WTF".

    And TL;DR

    I'm pretty sure it adds to the WTFery.

  • Franky (unregistered)

    so, the real question is, why did they not fix that damn modem?

  • Zacrath (unregistered)

    This theme on this article looks crap. Although the comments page looks better than usual.

  • Bleeeuuuuugh! (unregistered)


    FYI someones dog has vomited on your stylesheets.

  • Pista (unregistered)

    Token ring terminator??? WTF???

  • Coward (unregistered)

    God that was fucking awful. Just write the wtf. Don't fucking embellish it with pseudo Lovecraft crap. You're terrible writers and the only thing worse than terrible writers are writers that try to imitate their betters.

  • QJo (unregistered)

    It was not the tpyoes which finally caused his breakdown: he was a hardened website-reader and could brush these off with apolmb. The spellos were also not too bad a problem -- he could seperate himself from reality without his braincells being barbequed too badly.

    No -- what caused him to run screaming from the basement were the malapropisms. Their they were, to many of them for hymn two count, screaming viscously at him, coursing his brain to vapidify under the sprain and tern to blammange.

  • Old enough to have been there (unregistered)

    Would have been a more believable story if:

    a) flannel was mentioned. b) the USB stick is too new. If it was a CD, 5.25 inch floppy, 1/2 reel to reel mag tape or best 8 inch floppy it would have been more accurate. paper tape and punch cards written in EBCIDIC would have been quite geeky, but too old c) no mention of using tip or kermit?

  • QJo (unregistered)

    ... I actually fought the storey was grate. Can wee have moore?

  • Aonymous (unregistered)

    TRWTF is the author was a singer at Initech: "during my tenor at Initech" should be "during my tenure at Initech".

  • Guest (unregistered) in reply to Aonymous
    TRWTF is the author was a singer at Initech: "during my tenor at Initech" should be "during my tenure at Initech".

    Not to mention, you should EXORCISE a devil, not get it in shape :)

  • (cs) in reply to Pavv
    Seriously? This is crap. That guy^^ just summarized a 4000 word article in 25 words - and nothing was lost. Can anyone recommend a site that's like what DailyWTF used to be (ie not crap)?

    For once, I actually enjoyed the ridiculous embellishment--it's Halloween, dammit! The WTF itself wasn't much, but the Lovecraftian telling of it was definitely appropriate for today. The only thing that pisses me off is the black on black comments, but that's easily fixed.

    And, hey, at least it's not a Hanzo story.

  • Jo (unregistered)

    Heh. Haters are just gonna hate. Yeah, some glitches in that story and in the CSS. So what. Read it as a nod and a wink to Lovecraft, enjoy those reminiscences of Cthulhu, Azathoth, the Thing on the Doorstep and all those delightful horrors. Or fear them if you aren't of Richard Upton Pickman's mindset :-)

  • QJo (unregistered) in reply to Pavv
    Seriously? This is crap. That guy^^ just summarized a 4000 word article in 25 words - and nothing was lost. Can anyone recommend a site that's like what DailyWTF used to be (ie not crap)?

    This man reads War and Peace and remarks: "Seriously? Napoleon tried to invade Russia and failed. End of story. Why embellish it with pointless wittering about all these worthless people? I bet their all maid-up."

  • Anon 3:16 (unregistered)

    Hey, how about some freaking editing? This is some very raw crap.

  • QJo (unregistered) in reply to Guest
    TRWTF is the author was a singer at Initech: "during my tenor at Initech" should be "during my tenure at Initech".

    Not to mention, you should EXORCISE a devil, not get it in shape :)

    and my favourite: "a viscous but well deserved berating will burst forth from her."

    Buckets at the ready:

    I think it shoulc be "vicious", otherwise you glean the information that she had a heavy cold and was telling him off through a faceful of snot and phlegm. With every word, another grolly comes flying out of her mouth to land in our protagonist's face.

    Stomach empty? Good, my work is done.

  • Cthulhu (unregistered)

    This is just a rewritten dupe from http://thedailywtf.com/Articles/It_Must_Have_Been_Using_Those_Files.aspx

  • what (unregistered) in reply to Aris

    And this is how I learned that my RSS reader will do some really weird things when given feed items with liberally applied CSS.

  • (cs)
    Love the Lovecraftian embellishment. But the author really needs a proofreader. Listing only the worst of the atrocities, causing undescribable horrors when reading them:
    tenor at Initech telenet (it' s telnet, for *** sake!) Until they're notice. huberis
    TRWTF: Why had the f***ing stupid protagonist root access to the production server? And why didn't they use a more reliable network infrastructure?

    And WTF is this:

    Initech turned its new infrastructure and capabilities on Minitech, a large competitor, and swooped upon it to perform the inevitable and unavoidable acquisition.
    Shouldn't you complete the acquisition before turning your infrastructure and capabilities to a large competitor?
  • EvilSnack (unregistered) in reply to Old enough to have been there
    Old enough to have been there:
    Would have been a more believable story if:

    a) flannel was mentioned. b) the USB stick is too new. If it was a CD, 5.25 inch floppy, 1/2 reel to reel mag tape or best 8 inch floppy it would have been more accurate. paper tape and punch cards written in EBCIDIC would have been quite geeky, but too old c) no mention of using tip or kermit?

    Ditto that if this were on a USB stick, it can't be that old.

    But paper tape and punch cards aren't too old (certainly not too old to fit in a Lovecraft pastiche). The US military was still using paper tape in the late 80's.

  • (cs)

    TL;DR ...

  • Mark (unregistered)

    Tenor != tenure. Aaargh.

  • (cs) in reply to Cthulhu

    This is just a rewritten dupe from http://thedailywtf.com/Articles/It_Must_Have_Been_Using_Those_Files.aspx
    Good find. And even that original had a severe typo:

    Alex Papadimoulis:
    It was the eve of The Merge, a day that two companies (Intertrode and Initech) he dialed in to Intertode
    But in comparison to the current article this was a nice read! ("The Call of WTF" would be a nice read if the typos wouldn't destroy the reading experience).
  • Captcha: oppeto (unregistered)


  • The candyman (unregistered)

    "But I did not know how to exercise these devils."

    Usually I start them off with a slow four laps to get warmed up, then move on to calisthenics.

    If the Halloween candy we have were as over-elaborate as the prose here, there would be stomach aches throughout our ward.

    vulputate: The ablative of a third-declension adjective meaning "sort of like Marilyn Monroe as the she-wolf."

  • Ruben (unregistered)

    I, for one, liked the Lovecraft-ian style. It's halloween, and the writing was appropriate for it.

  • Omni (unregistered) in reply to Evo

    You deserve a prize! Here, have one internet =)

  • Amy (unregistered) in reply to Ruben

    Wow, tough crowd. Although I could have done without the black background too.

    WTF r'lyeh wgah'nagl fhtagn!

  • iWantToKeepAnon (unregistered)

    The RWTF is

    rm -i *
    then answer y/n for each file. Is it garbage? Answer y to delete. Look ok? Answer n to keep. Especially in the root, no scripting allowed there!!

  • fa2k (unregistered)

    It's not "exercise", it's "excise". (def. #2) 1. to expunge, as a passage or sentence, from a text. 2. to cut out or off, as a tumor.

    Don't know if it's appropriate usage or if someone has gone crazy with a thesaurus.

  • fa2k (unregistered) in reply to fa2k
    It's not "exercise", it's "excise".
    never mind, both were used
  • ExceptionHandler (unregistered)

    Too hard to read. I must be a masochist because I read the entire article even though I had to interpret the lovecraft crap. I kept seeing repetitiveness/redundancies, broken sentences, and inconsistencies. I should have just said TL;DR and be done with it. I guess that is TRWTF.

    Keep it concise and easy to read guys.

  • ceiswyn (unregistered)

    ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn?

    Also, I swear to Nyarlathotep, the next person I encounter who confuses 'viscous' and 'vicious' I am coming around there to give a practical demonstration...

  • (cs)
    1. Fixed comments. There are no comments before an article's posted. My bad.

    2. I changed a couple of the typos, but for the most part they're either intentional, or I don't care to change them. It's first person from the POV of someone manically trying to get the insanity on the paper.

    3. "I didn't like it". There, I just summarized your summary. You could have just said than and not used so many words. Why do you suck so much at criticism?

  • (cs) in reply to Cthulhu
    This is just a rewritten dupe from http://thedailywtf.com/Articles/It_Must_Have_Been_Using_Those_Files.aspx

    Ha! So it is. Though if our dupe rate is 1 per seven years...

  • Smug Unix User (unregistered)

    I enjoyed the story. It wasn't really a WTF. The protagonist was soaring on Icarus's wings wielding a power he did not properly respect. A server was sacrificed teaching a lesson which will not soon be forgotten.

    sudo -> "With great power comes great responsibility."

  • Fabian (unregistered)

    This... this is probably the best thing i've ever read in IT. Also Lovecraft :-)

Leave a comment on “The Call of WTF”

Log In or post as a guest

Replying to comment #420165:

« Return to Article