YES, THAT WOULD BE AWESOME



  •  Here's a little something to start the day... I just got a list of suggestions for new features for our internal ticket system. 99% of them are reasonable with the exception of this gem:

    "We should only write in uppercase. I think it'd be better cause it's faster".

    And to think I've specifically added code to this system to prevent all-uppercase entries. Something tells me this feature request will quietly be forgotten...



  • I'M SO SORRY FOR YOU...



  • HW ABT DRPPNG MST VWLS HLF WRDZ USNG RND ABBRVS 0 PNCTN 2 CAZ FSTR



  •  WTF STFU KTHXBY GTG TTYL



  • @DOA said:

    "We should only write in uppercase. I think it'd be better cause it's faster".
     

    TRWTF THAT WASNT WRITTEN IN UPPERCASE



  • @DOA said:

    "We should only write in uppercase. I think it'd be better cause it's faster".
     

    WELL, THATS BECAUSE IT IS. LOOK AT THIS POST, I JUST PRESSED CAPS-LOCK ONCE AND LOOK HOW FAST I CAN TYPE!!!



  • @DOA said:

    Something tells me this feature request will quietly be forgotten...
    TRWTF is your ticket system apparently doesn't have a "Rejected" status.



  • @Zagyg said:

    HWBTDRPNGMSTVWLSHLFWRDSNGRNDBRVS|.,:2CZFSTR

     

    FTFY,VRYBD KNWS U WST T MCH TM N SPCS & VWLS



  • @dtech said:

    @DOA said:
    "We should only write in uppercase. I think it'd be better cause it's faster".
    WELL, THATS BECAUSE IT IS. LOOK AT THIS POST, I JUST PRESSED CAPS-LOCK ONCE AND LOOK HOW FAST I CAN TYPE!!

    you know, you can solve that shift-key problem by using css. that way, even if you accidentally use the shift key, it'll still all be in uppercase.



  • @DOA said:

    I just got a list of suggestions for new features for our internal ticket system

    @DOA said:

    "We should only write in uppercase. I think it'd be better cause it's faster".

    @DOA said:

    And to think I've specifically added code to this system to prevent all-uppercase entries.

    Say, do you think it's possible that this is in fact somebody's tongue-in-cheek way of accusing you of being anal about the upper-case thing?()

    If not, then you've got a live one here.  You should troll them hard.  Make up a response.  Tell 'em that's not what your testing shows.  Write a little report.  Add a little table of figures supposedly showing relative system performance against datasets with a) all caps b) all lower c) mixed case 50-50 d) mixed case 20-80 caps e) mixed-case 80-20 caps.  Bonus points if you include a link to a rick-roll video in the references section or manage to include a shrunk-down version of the FSM pirates-vs-global-warming graph.  Ask 'em to explain their reasoning and show their test results.  See if you can troll them into wasting a day or two actually doing a whole bunch of testing with differing case datasets and watch them strain to show that there's some tiny improvement each time there's actually just a random blip in the measurement error.  DO IT FOR TEH LULZ!

    () - heh, I win an internets.  I managed to get 'anal' and 'tongue-in-cheek' into the same sentence.()
    (
    ) - And I didn't even have to stretch it to fit!



  • @Zecc said:

    @DOA said:

    Something tells me this feature request will quietly be forgotten...
    TRWTF is your ticket system apparently doesn't have a "Rejected" status.

    The feature request was FOR the Ticketing system, not sent through it.



  • I sit corrected.



  •  THE BIGGER LETTERS MOVE THROUGH THE WIRE FASTER AND PUSH THE SMALLER LETTERS OUT OF THE WAY.

     

    Now, back when the FCC madated that every telecomm have a pin on each account for customer rep access (meaning that you can't call a telecomm and get any informtion on your own account unless you create a pin, mail it to them or enter it via webapp and recite it whenver you call them). Now our first batch of PINs was mail only since the web app wasn't up yet, and some of them were all in uppercase. It just amazes me how some people who do data entry believe the ALL UPPERCASE is 'the computer way' or some shit lol...



  • @DaveK said:

    If not, then you've got a live one here.  You should troll them hard.  Make up a response.  Tell 'em that's not what your testing shows.  Write a little report.  Add a little table of figures supposedly showing relative system performance against datasets with a) all caps b) all lower c) mixed case 50-50 d) mixed case 20-80 caps e) mixed-case 80-20 caps.  Bonus points if you include a link to a rick-roll video in the references section or manage to include a shrunk-down version of the FSM pirates-vs-global-warming graph.  Ask 'em to explain their reasoning and show their test results.  See if you can troll them into wasting a day or two actually doing a whole bunch of testing with differing case datasets and watch them strain to show that there's some tiny improvement each time there's actually just a random blip in the measurement error.  DO IT FOR TEH LULZ!

    YES, THAT WOULD BE AWESOME



  • @Vechni said:

    Now our first batch of PINs was mail only since the web app wasn't up yet, and some of them were all in uppercase.
    There are uppercase numbers now?  What did they send in, stuff like "%$*^"?



  • for some reason they (the FCC or telecomm I once worked for) called it a PIN. it was just a passcode containing only alphanumerics, case insentive obviously since it can only be recited verbally.



  • @Flatline said:

    @Zecc said:

    @DOA said:

    Something tells me this feature request will quietly be forgotten...
    TRWTF is your ticket system apparently doesn't have a "Rejected" status.

    The feature request was FOR the Ticketing system, not sent through it.

    Then TRWTF is that the internal ticketing system isn't being used for feature requests. 



  • @bstorer said:

    There are uppercase numbers now?  What did they send in, stuff like "%$*^"?
     

    They're doing a rude number up in'ar



  • @Flatline said:

    @Zecc said:

    @DOA said:

    Something tells me this feature request will quietly be forgotten...
    TRWTF is your ticket system apparently doesn't have a "Rejected" status.

    The feature request was FOR the Ticketing system, not sent through it.

    Then I guess TRWTF is your lack of a meta-ticketing system, or the inability of your current ticketing system to handle recursion! 



  • @bstorer said:

    @Vechni said:

    Now our first batch of PINs was mail only since the web app wasn't up yet, and some of them were all in uppercase.
    There are uppercase numbers now?  What did they send in, stuff like "%$*^"?

    There's no need to swear.



  • Did this person have a previous job at a bank?



  • @Aaron said:

    Did this person have a previous job at a bank?
     

    What makes you say that?



  • COBOL makes you say that.



  • @Vechni said:

     THE BIGGER LETTERS MOVE THROUGH THE WIRE FASTER AND PUSH THE SMALLER LETTERS OUT OF THE WAY.N FCCNPINI ALL UPPERCASE

     

    ow, back when the madated that every telecomm have a pin on each account for customer rep access (meaning that you can't call a telecomm and get any informtion on your own account unless you create a pin, mail it to them or enter it via webapp and recite it whenver you call them). ow our first batch of s was mail only since the web app wasn't up yet, and some of them were all in uppercase. t just amazes me how some people who do data entry believe the is 'the computer way' or some shit lol...

    FTFY

     



  • EMPLOYEE HANDBOOK

    ...

    13) If employee is out for sick time, an e-mail should be sent to the manager and group before 10 am on the day of the sickness.

    ...

    24) For security reasons, employees may only send e-mail from their offices, not from off-site locations.

    ...

    38) If you should experience connectivity problems from your computer, please file a ticked by sending e-mail  to tickets@snafu.com.

     

    And, yes, I totally made that up :-)

     


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.