• Sauron (unregistered)

    throw new FristException("WTF?");

  • (nodebb)
    The chafing is just something you have to live with.

    Welcome to the world of software development.

  • Sauron (unregistered) in reply to Dragnslcr

    At this point, it's not even "software development" anymore, it's "WTFware WTFlopment"

  • (nodebb)

    Ref Sauron, it sure looks like nothing but Flopment to me. Pure unadulterated concentrated Flopment.

  • Rob (unregistered)

    The real WTF is string.Empty which is just "" but with more characters.

  • example (unregistered)

    I am only testing

  • (nodebb)

    Who are you to judge how Captain Underpants dresses?

  • Duston (unregistered) in reply to Rob

    But what if you want to put a setting in the Enterprise-y XML configuration file to define String.EMPTY as "File Not Found"? Whatever would you do?

  • kaejo (unregistered)

    What's strange about a generic exception handler (except for this brain-dead example?) If you get a truly unexpected exception which you can't rectify, for gods sake have a generic exception handler in the uppermost layer which logs/presents error to the user. What is really strange is the common Pokemon pattern.

  • Daemon (unregistered)

    Feels a bit like somebody wanted to have a way of setting up breakpoints when debugging but just ignore the exceptions in production...?

  • (nodebb)

    Yeah, this one is a fatality handler - so basically log it and tell the user to refresh or something, maybe calling the helpline with an reference code if there's even support available for this application. So in other words, there is no handling of different exceptions required, this should have been done long before an exception ends up there.

Leave a comment on “Exceptionally Backwards”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article