• pippo (unregistered)

    Permiere

  • someone (unregistered) in reply to pippo

    wow... no frist?

    probably lost it during the database sweep

  • DoEverythingMyself (unregistered)

    Ah yes, one of the worst situations to be in. When there's a mistake or a bug by your subcontractor, or in your third-party-purchased library (ahem ExtJS) but from your customer's perspective, its YOU who screwed up. This bites me in the a$$ very frequently. I've tried to read and study how to handle these types of issues (proj management, systems engineering, etc) but frequently the answer is "yep, it sucks".

    CAPTCH: illum(inated, which is what I need to be)

  • Nzall (unregistered) in reply to someone
    someone:
    wow... no frist?

    probably lost it during the database sweep

    There was a reader who displayed their pleasure at being the earliest commenter on this article. In the style of the article, he proceeded to indicate this in French, along with the customary spelling mistake to avoid the word filter.

  • DoEverythingMyself (unregistered)

    Ah yes, one of the worst situations to be in. When there's a mistake or a bug by your subcontractor, or in your third-party-purchased library (ahem ExtJS) but from your customer's perspective, its YOU who screwed up. This bites me in the a$$ very frequently. I've tried to read and study how to handle these types of issues (proj management, systems engineering, etc) but frequently the answer is "yep, it sucks".

    CAPTCH: illum(inated, which is what I need to be)

  • (cs) in reply to DoEverythingMyself
    DoEverythingMyself:
    Ah yes, one of the worst situations to be in. When there's a mistake or a bug by your subcontractor, or in your third-party-purchased library (ahem ExtJS) but from your customer's perspective, its YOU who screwed up. This bites me in the a$$ very frequently. I've tried to read and study how to handle these types of issues (proj management, systems engineering, etc) but frequently the answer is "yep, it sucks".
    Yes, your subcontrator screwed up, but guess what: it IS your fault, and the customer is correct to blame you because you outsourced it in the first place, and you picked the subcontractor. Beyond that, if you want to keep control over something, never put it into the control of someone else.

    I find it fairly ironic that your username is "DoEverythingMyself" given that the answer to your question is, "do everything yourself."

  • DoEverythingMyself (unregistered) in reply to jkupski

    LOL, yeah, that name was intentionally ironic, I am very self-aware that I need to address that. I do need to learn how to vett my subs better, and how to QC the whole system. Seems like SwissMedia needs to learn the same lesson with Datamaniaks.

  • (cs) in reply to DoEverythingMyself
    DoEverythingMyself:
    Ah yes, one of the worst situations to be in. When there's a mistake or a bug by your subcontractor
    Possibly the first mistake was made by the subcontractor, but the subsequent mistake was in my opinion made by Jeremy. You are in a difficult situation caused by a misunderstanding. Instead of making absolutely sure you do not run into the same problem again, he writes an e-mail, rather than getting the subcontractor on the phone, having him repeat every step back before proceeding, and staying on that line until the problem is solved. People mis-read their e-mails, if someone is clearly prone to doing so, trying to fix it with another e-mail is inviting disaster.

    And why did Jeremy not have a copy of the backup in the first place? Test-databases are meant to be mutilated, that's their whole point, odds are you will need to do a couple of restores before whatever procedure you intend to perform has been perfected.

  • the beholder (unregistered) in reply to DoEverythingMyself
    DoEverythingMyself:
    Ah yes, one of the worst situations to be in. When there's a mistake or a bug by your subcontractor, or in your third-party-purchased library (ahem ExtJS) but from your customer's perspective, its YOU who screwed up. This bites me in the a$$ very frequently. I've tried to read and study how to handle these types of issues (proj management, systems engineering, etc) but frequently the answer is "yep, it sucks".

    CAPTCH: illum(inated, which is what I need to be)

    Exactly what jkupski said.

    If your subcontractor screwed up, the customer has all the right to say you're at fault because he didn't choose the subcontractor. You (as in, your company) did, under the assumption that they would do a decent job. The fact that they didn't means it was (most likely) a poor job choosing which subcontractor to pick, ergo: YOUR fault.

    Granted, there could be ways they screwed up that couldn't be avoided, like them suddenly replacing all their staff with wet-behind-the-ears interns "analists". But from the customer's perspective it doesn't matter: you were hired to provide a job and you didn't.

  • Jim (unregistered)

    Wow, what database engine would allow you to move a database file that's in use?

  • (cs) in reply to DoEverythingMyself
    DoEverythingMyself:
    CAPTCH: illum(inated, which is what I need to be)
    "Illum" is actually the Maltese word for "today", and, appropriately in the context of the article, it is a now discontinued newspaper.
  • Smug Unix User (unregistered)

    Find the dependencies -- and eliminate them.

  • MrBester (unregistered) in reply to FragFrog
    FragFrog:
    Possibly the first mistake was made by the subcontractor, but the subsequent mistake was in my opinion made by Jeremy. You are in a difficult situation caused by a misunderstanding. Instead of making absolutely sure you do not run into the same problem again, he writes an e-mail....
    email in question:
    "Could you send me today’s 2AM backup when you get a chance?"

    That's pretty clear what is wanted and can't be chalked up to a "misunderstanding". Even if it was in French, "send" doesn't look anything like "restore"

  • anon (unregistered) in reply to Jim
    Jim:
    Wow, what database engine would allow you to move a database file that's in use?

    We all know that would never happen on a windows-box. If a process even thinks about maybe having access to a file, then that file's going to be there untill you reboot. I finally understand why.

  • ¯\(°_o)/¯ I DUNNO LOL (unregistered) in reply to Nzall
    Nzall:
    someone:
    wow... no frist?

    probably lost it during the database sweep

    There was a reader who displayed their pleasure at being the earliest commenter on this article. In the style of the article, he proceeded to indicate this in French, along with the customary spelling mistake to avoid the word filter.

    And it was lost when the thread was restored from a backup?

  • (cs)

    I'm gonna go with: Jeremy's the fool here.

    a) He sent an overly-casual email to his (3rd party) supplier with a request that assumed knowledge and experience. Everybody knows that if you want a 3rd party to do something, this has got to be a formally-raised request vith a copy sent to your boss (which of course means you got to fess up to pulling a boner in the first place, sux to be you innit).

    b) Having experienced the 3rd-party person fuck up really, really badly, he then learns his lesson and does not give him any further opportunity to fuck up again, using any techniques up to and including driving over there in a fucking Chieftain tank and demanding the head of the fuck-up on a pole to parade through the streets to frighten the fucking peasants from doing any such thing again.

    In practical terms, though, this includes what another geezer said up above, that he should guide the perpetrator step-by-step through exactly what he wants him to do, and make sure this is monitored really really carefully by both Jeremy and his boss andthe boss of the perpetrator of the original mistake.

    c) He should not have sent a caps-locked email because that will do one of two things. Either it will panic the guy at the other end who will then just hit keys at random and do even worse damage. Or it will anger the guy who will say "Who is this prick?" and then proceed to perform the most destructive act of sabotage he can possibly blame on the excuse of "simple mistake".

    The resulting termination of contracts is all well and good, and I would also make sure that Jeremy never ever gets put in a position where his job requires him to communicate with anyone apart from his immediate supervisor ever again.

  • deleted (unregistered)

    "SwissMedia outsourced their data storage"

    There's your problem.

  • (cs) in reply to Matt Westwood
    Matt Westwood:
    I'm gonna go with: Jeremy's the fool here.

    a) He sent an overly-casual email to his (3rd party) supplier with a request that assumed knowledge and experience. Everybody knows that if you want a 3rd party to do something, this has got to be a formally-raised request vith a copy sent to your boss (which of course means you got to fess up to pulling a boner in the first place, sux to be you innit).

    You would honestly expect to go through a full formally-requested procedure to restore a test database? Every single time? How soon would your boss be sick of getting CC'd in all of these... Isn't this sort of the point of a test database, to do things that could cause problems in a safe and easily restored environment?

    Perhaps I expect too much from other people but I would assume knowing the difference between words like "send" or "when you get a chance" and "overwrite a production database" to be a basic skill anyone would have.

    Matt Westwood:
    b) Having experienced the 3rd-party person fuck up really, really badly, he then learns his lesson and does *not* give him any further opportunity to fuck up again, using any techniques up to and including driving over there in a fucking Chieftain tank and demanding the head of the fuck-up on a pole to parade through the streets to frighten the fucking peasants from doing any such thing again.

    In practical terms, though, this includes what another geezer said up above, that he should guide the perpetrator step-by-step through exactly what he wants him to do, and make sure this is monitored really really carefully by both Jeremy and his boss andthe boss of the perpetrator of the original mistake.

    I would interpret "SEND ME A COPY OF THE PRODUCTION BACKUP, NOT RESTORE FROM BACKUP" as being a fairly specific instruction for even the most untrained monkey to deal with.

  • Paula (unregistered)

    I don't think BONER means what you think it means.

  • (cs) in reply to Matt Westwood

    [quote user="Matt Westwood"]a) He sent an overly-casual email to his (3rd party) supplier with a request that assumed knowledge and experience.[/quote]

    [quote user=Charles Robinson]“Hey, Sebastien,” his email started, “I’m sure I’ll have a good laugh about this later, but I totally trashed the test DB. Could you send me today’s 2AM backup when you get a chance?” He laid out the specific database backup he wanted, and where it needed to be delivered.[/quote]

    Maybe I'm just overly casual and assume too much, but I read that last sentence as saying that Jeremy laid out the specific database backup he wanted and where it needed to be delivered. The only assumption that I can see is that Jeremy is capable of reading and hasn't spent the entire morning eating paste.

    Perhaps he should have followed every sentence with the phrase "...and please don't erase any production data or set fire to any of the servers", and maybe his follow-up email should have included the words "Are there any grown-ups there with you? Can I speak with them?", but unless there was prior evidence that Jeremy had absolutely no clue of what he was doing, the original request looks reasonable.

    Addendum (2014-08-21 11:21): (What is unreasonable is that I can't format a quote tag properly. But don't worry, I'll just upload a new comment over top of the production database and that will fix everything.)

  • the way this is the real wtf (unregistered)

    this is the real wtf: this website still exist

  • the way this website SUCKS (unregistered)

    i went to what.tfwtf and i looked at comments people are being mean to blakey they have him tagged as "mediocre poster" u guys r just nothin but stupid haters

  • v (unregistered)

    what could jeremy have done with the backup to undo the restore anyway? nothing, that's what.

  • Taemyr (unregistered) in reply to DCRoss
    DCRoss:
    Matt Westwood:
    a) He sent an overly-casual email to his (3rd party) supplier with a request that assumed knowledge and experience.
    Charles Robinson:
    “Hey, Sebastien,” his email started, “I’m sure I’ll have a good laugh about this later, but I totally trashed the test DB. Could you send me today’s 2AM backup when you get a chance?” He laid out the specific database backup he wanted, and where it needed to be delivered.

    Addendum (2014-08-21 11:21): (What is unreasonable is that I can't format a quote tag properly. But don't worry, I'll just upload a new comment over top of the production database and that will fix everything.)

    You where missing quote marks around Charels Robinson. Why this destroyed the quote from Matt as well I have no idea.

  • (cs) in reply to Taemyr
    Taemyr:
    You where missing quote marks around Charels Robinson. Why this destroyed the quote from Matt as well I have no idea.

    The BBCode parser clearly prefers to take the Samson Option when interpreting tags. I believe that Jon Postel described it as the "Eff Robustness Principle" (or something like that)

    "Be conservative in what you send, but don't be afraid to pitch a fit if you see something you don't feel like accepting."

  • Random (unregistered) in reply to jkupski
    jkupski:
    DoEverythingMyself:
    Ah yes, one of the worst situations to be in. When there's a mistake or a bug by your subcontractor, or in your third-party-purchased library (ahem ExtJS) but from your customer's perspective, its YOU who screwed up. This bites me in the a$$ very frequently. I've tried to read and study how to handle these types of issues (proj management, systems engineering, etc) but frequently the answer is "yep, it sucks".
    Yes, your subcontrator screwed up, but guess what: it IS your fault, and the customer is correct to blame you because you outsourced it in the first place, and you picked the subcontractor. Beyond that, if you want to keep control over something, never put it into the control of someone else.

    I find it fairly ironic that your username is "DoEverythingMyself" given that the answer to your question is, "do everything yourself."

    Isn't that the opposite of ironic?

  • konnichimade (unregistered) in reply to Random
    Random:
    jkupski:
    DoEverythingMyself:
    Ah yes, one of the worst situations to be in. When there's a mistake or a bug by your subcontractor, or in your third-party-purchased library (ahem ExtJS) but from your customer's perspective, its YOU who screwed up. This bites me in the a$$ very frequently. I've tried to read and study how to handle these types of issues (proj management, systems engineering, etc) but frequently the answer is "yep, it sucks".
    Yes, your subcontrator screwed up, but guess what: it IS your fault, and the customer is correct to blame you because you outsourced it in the first place, and you picked the subcontractor. Beyond that, if you want to keep control over something, never put it into the control of someone else.

    I find it fairly ironic that your username is "DoEverythingMyself" given that the answer to your question is, "do everything yourself."

    Isn't that the opposite of ironic?

    He means it's ironic that "DoEverythingMyself" doesn't do everything himself :|

  • (cs) in reply to the way this website SUCKS
    the way this website SUCKS:
    i went to what.tfwtf and i looked at comments people are being mean to blakey they have him tagged as "mediocre poster" u guys r just nothin but stupid haters

    The badge that he set as his title?

  • dignissim (unregistered) in reply to Paula
  • (cs) in reply to DoEverythingMyself
    DoEverythingMyself:
    Ah yes, one of the worst situations to be in. When there's a mistake or a bug by your subcontractor, or in your third-party-purchased library (ahem ExtJS) but from your customer's perspective, its YOU who screwed up. This bites me in the a$$ very frequently. I've tried to read and study how to handle these types of issues (proj management, systems engineering, etc) but frequently the answer is "yep, it sucks".

    CAPTCH: illum(inated, which is what I need to be)

    And you can just guarantee that you weren't in the meeting where management decided to use that vendor's software which, six months down the line, you could have built yourself.

    AND your version would be more maintainable, cheaper to build, and generally a better use of time than acting as a liaison between your dumba$$ vendor, whose first instinct to any questions is to get defensive, and the client who has a lot of questions, because your vendor's only marketable skill is overselling their useless software, which you're now stuck with until apparently the end of time.

  • (cs)

    He's lucky (?) was a small database. We have a few where I work that would present a real challenge for any email system.

    ("Your mailbox is currently over your assigned limit of 1 gigabyte by 12.4 terabytes. You will be unable to send any messages until you reduce the size of your mailbox below your limit.")

  • AnOldHacker (unregistered)

    Jeremy is clearly the Prime WTFer in this scenario.

    1. If YOU are working with a test DB, then YOU ensure that you have the ability to instantly restore from snapshot, not take lunch.

    2. The "Forgotten WHERE" is NOT a classic boner. The classic boner is "Forgotten WHERE outside a transaction", which is only a serious problem if the original "Forgotten test SELECT prior to UPDATE to ensure I don't hose the entire table" occurs.

    3. On what planet does "sub made a mess" combined with "customer is angry" not imply "get the boss". At the very minimum, the boss can be placating the customer while you work the problem. Or maybe he can work the sub while you placate the customer. That's what a boss's job is. To make those kind of decisions.

    4. As mentioned, TYPING IN ALL CAPS IS A POOR WAY TO COMMUNICATE. But really, it has taken a lot of discipline to avoid it in this case.

    If I were Jeremy, I would be worrying about my own contract...

  • (cs)

    1. Yes, he should have had a local copy of the database, and restored from that.

    2. He should have not "gone for coffee" -- should have stayed on the line while the database was restored. And verified that what was being done was the correct procedure.

    3. The french guy should have said -- wait, I'm going to restore the production database from the backup. Are you sure that's what you want???

    4. The "2AM" backup, for someone in the US, is probably a different backup than the "2AM" backup for the guy in France (by about 8 hours or so). So specifying exactly which backup, is important.

    5. Why does a 3rd-party contract guy have write access to the production database? With enough privs to restore from backup? Sure, give him access to muck with the individual tables, maybe, but not the ability to completely gut the database.

  • (cs) in reply to MrBester
    MrBester:
    That's pretty clear what is wanted and can't be chalked up to a "misunderstanding". Even if it was in French, "send" doesn't look anything like "restore"
    The reply made it equally clear that the contractor thought he had done as requested. Perhaps Jeremy's original e-mail was indeed abundantly clear, or perhaps the version we see here has been editored, but in either case, the simple fact of the matter is that someone on the receiving end did not do what Jeremy wanted him to do (but still *thought* he had done what Jeremy wanted him to do).

    When you are in a critical situation, and you know that someone you are communicating with has trouble understanding your instructions (be they ever so clear), the thing to do is either step in and fix things yourself, or to make absolutely sure that the person on the receiving end is completely clear on what you want him to do. Not: "fire off a quick e-mail and leg it".

    We do not know why the miscommunication happened, but that it happened twice, between the same two people, would support the notion that at least one of them has trouble communicating - or that the contractor is a complete and utter idiot, which is only more reason not to trust him and to watch his every mouse-click.

    Hell, if I just caused a major problem for a big (?) client that could in theory be fixed in about ten minutes, I would not even dream of going for lunch until I had seen to it that the crisis was averted (and that everyone involved was informed, the solution tested, and no immediate additional problems were expected). Of course, the way articles on here get rewritten, this might just have been an attempt at making a complete story out of a two-sentence twitter message.

  • Sean (unregistered) in reply to Matt Westwood

    To say that Jeremy never communicates with anyone aside from his immediate supervisor ever again is very extreme. How does one have the chance to learn with those sorts of consequences?

    You need to raise a couple of children. That'll wise you up.

  • (cs) in reply to Sean
    Sean:
    To say that Jeremy never communicates with anyone aside from his immediate supervisor ever again is very extreme. How does one have the chance to learn with those sorts of consequences?

    You need to raise a couple of children. That'll wise you up.

    Communicating on here feels like raising a couple of fucking children.

    But seriously folks, this sort of behaviour is career-limiting to such an extent ("Oh look, here's the guy that lost us the biggest contract we've ever had by his complete inability to communicate!") that his bozo bit has now been well and truly set -- at least in the company he currently works for.

    The only way to get out from under this embarrassment is by leaving and going somewhere to make a completely new start.

  • Evan (unregistered) in reply to FragFrog
    FragFrog:
    Hell, if I just caused a major problem for a big (?) client that could in theory be fixed in about ten minutes, I would not even dream of going for lunch until I had seen to it that the crisis was averted...
    The lunch was before the crisis; the only thing affected when Jeremy went to lunch was Jeremy.
  • Cheong (unregistered) in reply to jkupski

    Indeed. The first rule of outsourcing is "Don't ever think of outsourcing anything related to your core business".

    If contractor messed up and caused problem to your critical operation, it's your fault.

  • Cheong (unregistered) in reply to FragFrog
    FragFrog:
    Possibly the first mistake was made by the subcontractor, but the subsequent mistake was in my opinion made by Jeremy. You are in a difficult situation caused by a misunderstanding. Instead of making absolutely sure you do not run into the same problem again, he writes an e-mail, rather than getting the subcontractor on the phone, having him repeat every step back before proceeding, and staying on that line until the problem is solved. People mis-read their e-mails, if someone is clearly prone to doing so, trying to fix it with another e-mail is inviting disaster.
    In my personal experience, if communication is the problem, talking on phone instead of using emails makes in worse.

    With email you get it black and white, with additional benefit of able to CC the email to his supervisor and manager at the same time to make sure recovery step is properly supervised.

  • jeremysucks (unregistered)
    new, shiny, PHP5
    How old is this submission?
    Jeremy committed the dreaded “forgotten WHERE clause” boner. His local copy of the French-Haitian News DB became unusable. He immediately reached out to Sebastien to help remedy the situation.
    Jeremy fucks with his copy of the production db without making a backup. Maybe they should outsource Jeremy's position.
    I’m sure I’ll have a good laugh about this later, but I totally trashed the test DB. Could you send me today’s 2AM backup when you get a chance?”
    A busy person skimming this sentence easily misunderstand....or judging by Jeremy's ineptitude, maybe the production DB was named "Test"?
    Jeremy engaged his Caps Lock key and replied, “THAT IS NOT WHAT I AKSED FOR SEBASTIEN.
    "Jeremy" fucks up his only copy of a db doing stupid shit, then lashes out at the only person who can help him at this point using all caps and shitty spelling. GODDDAMN OTHRE POEPLE!
    "It was a long road to cleaning up the disaster."
    Longer than sending the copy of the database right back to them? Let me guess - before he thought of that Jeremy ran the same "boner" query on the last remaining copy of the db.
  • Gladys Fieldberg (unregistered)

    Finally, a real WTF!? after two boring not-really-WTFs.

  • (cs) in reply to Gladys Fieldberg
    Gladys Fieldberg:
    Finally, a real WTF!? after two boring not-really-WTFs.
    Nah. Just one that you've got the expertise to understand. The one with copying vtables about was catastrophically bad, but required a substantial background in C++ to appreciate.
  • (cs) in reply to DrPepper
    DrPepper:
    5. Why does a 3rd-party contract guy have write access to the production database? With enough privs to restore from backup? Sure, give him access to muck with the individual tables, maybe, but not the ability to completely gut the database.
    Would it be better to outsource your DBA work to a 3rd party, but not allow them the privileges that, say, a DBA would need?
  • (cs) in reply to DrPepper
    DrPepper:
    3. The french guy should have said -- wait, I'm going to restore the production database from the backup. Are you sure that's what you want???
    Yes, not double-checking before overwriting prod is certainly one of the WTFs.
    DrPepper:
    4. The "2AM" backup, for someone in the US, is probably a different backup than the "2AM" backup for the guy in France (by about 8 hours or so). So specifying exactly which backup, is important.
    But here the WTF is thinking that anyone in this story is in the US. Jeremy (French name, employee of a company called SwissMedia) is writing to Sebastien (French name, employee of SwissMedia's subcontractor). There's no good reason to suppose that they're not both in the Central European timezone. (And while the client is probably in Haiti, that's not the US).

    It's true that there could potentially be confusion between CE(S)T and UTC, but a) this isn't the first communication about copies of backups of prod, because Jeremy had one to bork, so there's some context which might imply a timezone to those who know it; b) Jeremy is asking for a copy to restore over his test DB. He probably doesn't care whether it's a copy of the 02:00 UTC backup or the 02:00 CE(S)T backup.

  • (cs)

    Why is every paragraph SEXY?

  • Name (unregistered)

    The wtf site seems to have had a SEXY make over recently

  • fatfacemcfattypants (unregistered) in reply to spenk
    spenk:
    Matt Westwood:
    I'm gonna go with: Jeremy's the fool here.

    a) He sent an overly-casual email to his (3rd party) supplier with a request that assumed knowledge and experience. Everybody knows that if you want a 3rd party to do something, this has got to be a formally-raised request vith a copy sent to your boss (which of course means you got to fess up to pulling a boner in the first place, sux to be you innit).

    You would honestly expect to go through a full formally-requested procedure to restore a test database? Every single time? How soon would your boss be sick of getting CC'd in all of these... Isn't this sort of the point of a test database, to do things that could cause problems in a safe and easily restored environment?

    Perhaps I expect too much from other people but I would assume knowing the difference between words like "send" or "when you get a chance" and "overwrite a production database" to be a basic skill anyone would have.

    Matt Westwood:
    b) Having experienced the 3rd-party person fuck up really, really badly, he then learns his lesson and does *not* give him any further opportunity to fuck up again, using any techniques up to and including driving over there in a fucking Chieftain tank and demanding the head of the fuck-up on a pole to parade through the streets to frighten the fucking peasants from doing any such thing again.

    In practical terms, though, this includes what another geezer said up above, that he should guide the perpetrator step-by-step through exactly what he wants him to do, and make sure this is monitored really really carefully by both Jeremy and his boss andthe boss of the perpetrator of the original mistake.

    I would interpret "SEND ME A COPY OF THE PRODUCTION BACKUP, NOT RESTORE FROM BACKUP" as being a fairly specific instruction for even the most untrained monkey to deal with.

    I agree.

    Unless your shop has some very serious competency problems, servers and code/VCS are easily backed up and restored.

    Although it can vary based one what you are doing, usually data is the most important thing and can be the hardest to back up well or restore quickly. There's a lot of it, it has the highest rate of change and it's hard or impossible to replace (redo, etc). If they outsourced it to idiots, they have a big problem.

    Language barrier could be a problem but it sounds to me like this Sebastion characters never should have been let near a database in the first place.

    Otherwise it's like saying a patient is supposed to tell the surgeon exactly what to do or saying the passengers of a plane need to tell the pilot which controls to operate. You some occupations, you don't hire untrained people or people that can't follow/interpret instructions unless you have a death wish.

  • Bob (unregistered) in reply to Matt Westwood
    Matt Westwood:
    He should not have sent a caps-locked email ... or it will *anger* the guy who will say "Who is this prick?" and then proceed to perform the most destructive act of sabotage he can possibly blame on the excuse of "simple mistake".
    He did? Trashing the entire website was the rest of the story.
  • (cs)

    I am loving this story, but some mysteries are not yet resolved

  • Evan (unregistered) in reply to dkf
    dkf:
    Gladys Fieldberg:
    Finally, a real WTF!? after two boring not-really-WTFs.
    Nah. Just one that you've got the expertise to understand. The one with copying vtables about was catastrophically bad, but required a substantial background in C++ to appreciate.
    Wait I don't remember that one; it sounds promising. The closest I could find was http://thedailywtf.com/Comments/The-Interface.aspx (and this amazing sidebar: http://forums.thedailywtf.com/forums/p/26897/309222.aspx).

Leave a comment on “Non-Restorative Restoration”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article