• (disco)

    http://thedailywtf.com/images/15/q4/e190/Pic-5.jpg

    SPANK SPANK! Naughty user!

    We must teach him not to use inappropriate spaces for when we "forgot" calling trim in the next few screens of our wizards.

  • (disco)

    insert memory card

    No, into your card reader!

  • (disco)

    Had a customer once who had the temerity to complain to us when we gave him an app that threw him out when he entered data which was inappropriately formatted (e.g. had spaces where we didn't approve of spaces, didn't include spaces where we wanted him to have spaces, entered dates with the wrong delimiters (we needed / when he entered - ) and so on. We pointed out that none of this was given to us in the specification he supplied us, so: tough.

  • (disco) in reply to Jaloopa

    insert memory card

    :giggity:

  • (disco) in reply to Jaloopa

    Insert memory card to the tachograph of your car to continue.

    When you leave the area, please remember to put the card into collecting slot as you pay the fee. We'll charge you for over-speeding if you dare to do so here. Thank you.

    :trolleybus:

  • (disco) in reply to JBert

    So our deployment process (which is trwtf) has a step that involves out ops team copying info out of a configuration document into the actual configuration UI. Some times they have to make a decision, but doing that requires reading the fucking doc and paying attention to the things they're copy pasting.

    After a couple of botched deploys where decisions were not made, we noted that those same deploys had leading and trailing whitespace from the doc in most of their configuration fields. We decided that whitespace was a symptom of not doing their fucking job correctly and added validation to those fields. Instead of trimming, we refuse submits with whitespace.

    We are trying to quite literally train attention to detail into our users.

  • (disco) in reply to Weng
    Weng:
    So our deployment prices (which is trwtf)

    You have to pay to deploy? Yes, that is TRWTF.

  • (disco) in reply to NedFodder

    Blah. Fucking mobile keyboards

  • (disco) in reply to Quite
    Quite:
    None of this was given to us in the specification he supplied us, so: tough.

    The robustness principle in computer science bids us to be conservative in what we send and liberal in what we accept. This is especially important in the user interface. The next time you receive a specification that doesn't follow basic UI principles like accepting badly formed user input if the intent is obvious, I'd recommend asking some questions. It may be that the client, as in this case, simply didn't consider the matter.

    Weng:
    We are trying to quite literally train attention to detail into our users.
    In this case the intent is not obvious (i.e. do they really want to use these particular settings?), so it makes sense to be more restrictive about the input.
  • (disco) in reply to Weng
    Weng:
    Instead of trimming, we refuse submits with whitespace.

    There are programs (Word, Outlook) that automatically select trailing spaces when you double-click a word. If I were using your pricesprocess, and copy-pasting from Word to your UI, and you made me manually remove all those trailing spaces, I'd punch you in the face.

  • (disco) in reply to NedFodder

    It's the ops team's process. We put the settings in a word doc because that's what they asked for. Problems with their processes are not my problem.

    Plus, the spaces weren't always trailing. There were sometimes leading. Sometimes trailing. Sometimes both. Once or twice the first or last character were missing. I swear to christ they must have been actually click-drag selecting.

  • (disco) in reply to Weng
    Weng:
    click-drag selecting

    This is also broken in Word and Outlook.

    Weng:
    It's the ops team's process

    Yeah, back to your original point before I made fun of your typos, that's TRWTF.

  • (disco) in reply to Weng
    Weng:
    We are trying to quite literally train attention to detail into our users.
    Like usual, truth is stranger than fiction. :facepalm:
  • (disco)

    There was an error when transferring the comment to the HTTP server.<DISCOURSE!> Thanks a lot for the help.

  • (disco)

    Regarding the Ethernet switch - perhaps the French count ports in base-18 :stuck_out_tongue_winking_eye:

  • (disco)

    I think we've seen that "thanks a lot for the help" message before. Protip: don't make your messages even remotely have the possibility of sounding sarcastic, lest they be taken as such...

  • (disco)

    Regarding the switch in the first picture, what the hell is a "gibabit"?

  • (disco) in reply to sloosecannon
    sloosecannon:
    that "thanks a lot for the help" message before

    I know VLC has it. Where else does it appear?

  • (disco) in reply to Tsaukpaetra

    FileZilla I think.... I may be wrong on that though...

  • (disco) in reply to peanutt
    peanutt:
    what the hell is a "gibabit"?

    That stupid set of -ibi- prefixes, spelled wrong.

  • (disco) in reply to peanutt
    peanutt:
    What the hell is a "gibabit"?

    1036870912 bits

  • (disco) in reply to FrostCat

    For a while (before the -ibi- stuff got prominent) my dad liked to joke about gigglebytes.

  • (disco) in reply to jkshapiro
    jkshapiro:
    peanutt:
    What the hell is a "gibabit"?

    1036870912 bits

    [image]
  • (disco)
    Steve L. wrote, "Hey AT&T! The 'Trim' function in JavaScript would work GREAT here."
    TIL JavaScript has actually officially added a trim() function. I guess I can finally start thinking about removing the 
    String.prototype.trim = function(){...}

    stuff from my projects that don't need to support IE8 anymore.

  • (disco) in reply to peanutt

    Gib-a-bit is German for "give a bit" so that should be 1b/s. Iow. you might get a few more ports in English but they are vastly slower than the french ones.

  • (disco) in reply to NedFodder
    NedFodder:
    There are programs (Word, Outlook) that automatically select trailing spaces

    ...even when there aren't any to select, and especially when you DON'T want them. That is TRWTF.

    Weng:
    There were sometimes leading. Sometimes trailing.

    Seen that too. -_-

  • (disco) in reply to redwizard

    https://github.com/tdwtf/WtfAds/blob/9720300be8ab8c71f146bbcac3997f8488487ff1/urls.xml#L9

  • (disco) in reply to peanutt

    It's a gigabit in Canadian English spelling I guess.

  • (disco) in reply to ben_lubar

    They must have copy-pasted from Word.

  • (disco)

    Signed up to post this. TRWTF is the memory card picture is upside down? [image]

    Also, why does Discourse want both my sex and gender? "Sorry, new users can only put 1 image in a post."

  • (disco) in reply to Qvazar

    Yay phone orientation and EXIF?

  • (disco) in reply to Qvazar

    Oddly enough, it displays correctly in the article for me (Chrome on Windows), but opening the image directly in Chrome or Windows Photo Viewer displays it upside-down.

    Somewhat fitting for a picture of an Australian airport.

  • (disco) in reply to Qvazar
    Qvazar:
    Also, why does Discourse want both my sex and gender?

    Custom fields became a feature, we couldn't pick which one to add, so we added both. Most users either don't fill them or put in jokes.

  • (disco) in reply to PleegWat

    Yup, one of the, ahem, perks of TDWTF style usage is that you can't ever expect the expected.

  • (disco) in reply to Arantor

    Features will generally be used, but preferably not in a way that makes any belgium­ing sense to Jeff and friends.

  • (disco) in reply to PleegWat

    'used' is the wrong word, 'abused' is the correct one, I feel.

  • (disco) in reply to Arantor
    Arantor:
    phone orientation

    It's the phone's choice and should be respected.

Leave a comment on “End User Experience May Vary by Region”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article