• Cyp (unregistered)

    I chan't see the problem with that code.

  • Welcome to English (unregistered)

    Learn it, love it, laugh at others who do not no how to write it.

  • cDub (unregistered)

    String.ToUpper? Anyone?

  • Nagesh (unregistered)

    I am not expert in VB, but I do not see problem here.

  • (cs) in reply to Nagesh
    Nagesh:
    I am not expert in VB, but I do not see problem here.
    VB.
  • Nagesh (unregistered) in reply to Welcome to English
    Welcome to English:
    Learn it, love it, laugh at others who do not no how to write it.
    I have teacher who say this problem easily overcome by drils of comonly mispeled werds.
  • drusi (unregistered)

    This is the first time I've ever seen a program that's secure against evil chancellors.

    Captcha thinks this should become a conventiono way of writing code.

  • yo (unregistered) in reply to Nagesh
    Nagesh:
    I am not expert in VB, but I do not see problem here.

    And that's why outsourced code sucks.

  • drusi (unregistered) in reply to drusi
    drusi:
    This is the first time I've ever seen a program that's secure against evil chancellors.

    Captcha thinks this should become a conventiono way of writing code.

    Sorry, I mean "conventio." Stupid familiarity.

    Captcha thinks we should have split the difference back in the pre-Unicode days and used "acsi."

  • Nagesh (unregistered) in reply to yo
    yo:
    Nagesh:
    I am not expert in VB, but I do not see problem here.

    And that's why outsourced code sucks.

    That's why your martyrchord. My company score many contracs outperforming your silly games.

  • (cs)

    Obvosly, the button was given a lable called "chancel", without rhym or reason, and its prolly too difficult to change teh common tpyo in the code.

  • Spoe (unregistered)

    So: No, Continue, Altar?

  • (cs)

    At least this would be easy to fix, right? Perhaps I'm being nave, but I think that code would be easy to altar.

  • QJ (unregistered)

    Clear as chrystal, that code.

    Or as we say, when it does the job perfectly, it "goes to church".

  • C-Octothorpe (unregistered) in reply to Nagesh
    Nagesh:
    I am not expert in VB, but I do not see problem here.

    The medium is the message...

  • QJ (unregistered) in reply to dgvid
    dgvid:
    At least this would be easy to fix, right? Perhaps I'm being nave, but I think that code would be easy to altar.

    I think aisle agree.

  • foo (unregistered)

    "Chancel" is perfectly cromulent. The button by chance either cancels the operation or doesn't. Many applications have such a feature, but few dare name it correctly.

  • what (unregistered) in reply to Cyp
    Cyp:
    I chan't see the problem with that chode.

    FTFY

  • (cs) in reply to foo
    foo:
    "Chancel" is perfectly cromulent. The button by chance either cancels the operation or doesn't. Many applications have such a feature, but few dare name it correctly.

    Actually, most Cancel buttons don't work at all and are just there to give a calming sense of cancelability. In my experience, at least.

  • (cs)

    Um, it's pronounced khan' səl.

  • Sten (unregistered)

    So they finally found the file in chancel and corrected the peviously seen “Yes”, “No”, “File not Found”.

    Captcha: esse. Yes, I’m eating German food right now.

  • Rob (unregistered)

    I guess the original coder thought there was no chancel that the typo would be caught?

  • (cs) in reply to JamesQMurphy

    Khaaaaaaaaaaaan!!! səl?

  • (cs)

    Yawn. I expect this shit from VB.

  • (cs)

    I'm interested in what Connector.Connection.PressItem() does. It looks like the code is performing some user action, which makes this a very Visual Basicy design indeed.

  • Nagesh (unregistered) in reply to Lorne Kates
    Lorne Kates:
    Obvosly, the button was given a lable called "chancel", without rhym or reason, and its prolly too difficult to change teh common tpyo in the code.
    You would not have been to complete grade 6 in India with that grammer problems!
  • Dave-Sir (unregistered) in reply to Lockwood

    I've done far worse than kill you, I've hurt you. And I wish to go on hurting you. I shall leave you as you left me, as you left her. Marooned for all eternity, at the center of a dead planet. Buried alive.

    Lockwood:
    Khaaaaaaaaaaaan!!! səl?
  • kktkkr (unregistered)

    I hate your chomments. It's a chommon mistake in chomputer chode. Get over it.

    (my chaptcha is acsi too!)

  • (cs)

    At my office they hired a guy and his first job was to write tests for the shiny new testing framework I had made. Problem was he didn't really know 100% how many of our classes SHOULD act, so he wrote tests for how they WERE acting, even if the behavior was wrong (that was part of the reason we wanted tests, we knew there were going to be a lot of edge cases that were not working). A number of times I fixed a bug only to find multiple tests now failed, and I'd have to go in and look and find bad assumptions about how the class being tested worked. Other times it was just undefined scenarios that it assumed were defined.

    Not the guy's fault totally; whoever is the most familiar with any particular class should have written the tests for it.

  • (cs) in reply to frits
    frits:
    I'm interested in what Connector.Connection.PressItem() does. It looks like the code is performing some user action, which makes this a very Visual Basicy design indeed.
    "test automation framework"
  • (cs) in reply to D-Coder
    D-Coder:
    frits:
    I'm interested in what Connector.Connection.PressItem() does. It looks like the code is performing some user action, which makes this a very Visual Basicy design indeed.
    "test automation framework"

    Point well-taken.

  • puppets (unregistered) in reply to The MAZZTer
    The MAZZTer:
    At my office they hired a guy and his first job was to write tests for the shiny new testing framework I had made. Problem was he didn't really know 100% how many of our classes SHOULD act, so he wrote tests for how they WERE acting, even if the behavior was wrong (that was part of the reason we wanted tests, we knew there were going to be a lot of edge cases that were not working). A number of times I fixed a bug only to find multiple tests now failed, and I'd have to go in and look and find bad assumptions about how the class being tested worked. Other times it was just undefined scenarios that it assumed were defined.

    Not the guy's fault totally; whoever is the most familiar with any particular class should have written the tests for it.

    50% that guys fault for making assumptions which were probably quite clearly incorrect.

    50% the previous devs fault for not documenting/commenting the code to make it clear what the intention/purpose was.

  • lobsterchord (unregistered)

    I thought perhaps Amy Winehouse wrote it.

  • bitterman0 (unregistered)

    "Chancel" nothing. My favorite so far is "Do you shure?" (where "Are you sure?" prompt was appropriate).

  • Nagesh (unregistered) in reply to bitterman0
    bitterman0:
    "Chancel" nothing. My favorite so far is "Do you shure?" (where "Are you sure?" prompt was appropriate).

    I'm glade you enjoyed it

  • (cs)

    I keep reading misericord.

  • Dave (unregistered) in reply to D-Coder

    I'm fairly certain the VB EULA precludes all of the following: = tests = automation [that is useful] = frameworks [that take less than 50MB]

  • iToad (unregistered)

    This really turns the clock back for me. All the way back to 1966. Back to the days of my first bug. I remember it well. I proudly submitted my first Fortran program (on punched cards) to the UNIVAC-1108 operator, and discovered much to my surprise that 'PROCEDURE' is not spelled with two 'E's.

    I have made many errors and generated many bugs since then, but I will always remember the first one. It has a special place in my heart.

  • (cs)

    At first glance, it looks like a logic bug. There appears to be a check for variations on spelling of the same word, but only a handful of cases are considered, inexplicably obvious other cases are ignored.

    Upon reflection, however, I think I see this is not a WTF. It appears the developer wanted to allow SPECIFICALLY those variations of values, in anticipation of future functionality TBD - perhaps in later versions, buttons of the same word but different character cases might perform different actions.

    Fx, "NO" could perform a different function than "No", but the programmer isn't sure what that will be in the future, so for the time being s/he's just assigning them to the same software state.

  • ABBA (unregistered)

    If you change your mind, I'm the first in line. Honey I'm still free, Why not chancel me?

  • LANMind (unregistered)

    There are an infinite number of monkeys typing on an infinite number of typewriters, and this thread is nothing like Shakespeare.

  • cheap nfl trolls (unregistered) in reply to LANMind
    LANMind:
    There are an infinite number of monkeys typing on an infinite number of typewriters, and this thread is nothing like Shakespeare.
    For this comment, inspired me, feeling this author words into my heart.
  • (cs) in reply to bitterman0
    bitterman0:
    "Chancel" nothing. My favorite so far is "Do you shure?" (where "Are you sure?" prompt was appropriate).

    We had an application which, whenever anything went wrong (and it was fussy about the files it ate) used to issue the user message:

    oh bugger

  • (cs)

    Aha! I get it! The real WTF is that "Continue" has two apostrophes in front of it when it really only needs one!

    Excellent! I do believe I'm learning this programming malarkey!

  • Hater (unregistered)

    This buttons were obviously for a church application.

    No, I have nothing to confess.

    Continue, I would like to confess through email.

    Chancel, I would like to book an appointment to confess at a chancel.

  • (cs) in reply to Hater
    Hater:
    This buttons were obviously for a church application.

    No, I have nothing to confess.

    Continue, I would like to confess through email.

    Chancel, I would like to book an appointment to confess at a chancel.

    +1

  • CurtCharlesPDX (unregistered)

    Reminds me of a conversation in Japan where the engineer kept telling me about the crutch. Took me a good 15 minutes before I realized he meant clutch.

  • Auge (unregistered) in reply to CurtCharlesPDX
    CurtCharlesPDX:
    Reminds me of a conversation in Japan where the engineer kept telling me about the crutch. Took me a good 15 minutes before I realized he meant clutch.
    I used to think it was an accent when they said "crap their hands." I'm never eating at another Chinese restaurant as long as I live.
  • (cs)

    What's up with the comment purge?

  • ÃÆâ€℠(unregistered)

    Ah, I found TRWTF. It should be kancel, instead of chancel.

Leave a comment on “No, Continue, Chancel?”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article