• Mark Wilden (unregistered) in reply to Arancaytar

    There is nothing in that software that evades taxes or defrauds customers. Nor must a software vendor be a tax lawyer (unless the client pays them to be one).

  • Boz (unregistered) in reply to Thing that goes *toot* in the night
    Thing that goes *toot* in the night:
    Some damn Yank:
    messer:
    The Corrector:
    Robb:
    the real wtf is Texas
    FTFY

    Texas should be illegal.

    In 49 states Texas is illegal.

    So, all of them except Hawaii?

    so Texas is illegal... in Texas ??

  • Fernando (unregistered)

    Uncle Sam doesn't ever get a cut of a retail transaction. Sales taxes are levied by states, not by the federal government.

  • Grrr (unregistered)
    No touch-screens, no graphics and no cashier-friendly reminders; just a plain old text-based interface with obscure keyboard commands for navigation.

    Actually, I am fairly sure, that prior to touchscreens at least, any windows-based POS was way worse than plain old text-based interface that didn't use a mouse.

    I remember looking at the way it was in 1980ies, when at a medical lab I saw the people enter blood-sample test results into computer. No robots for blood test at that time, and no GUI for computer (a WANG minicomputer).

    They could really enter loads of results very quickly, because they only had a number of keyboard shortcuts to remember, like: test 621, patient 112, results 11.2 [enter] 7.5 [enter]

    Then they got upgraded to some windows-based soft several years later, and had to use mouse to move from entry field to entry field... the productivity went down by a mile.

  • (cs) in reply to Grrr
    Grrr:
    No touch-screens, no graphics and no cashier-friendly reminders; just a plain old text-based interface with obscure keyboard commands for navigation.

    Actually, I am fairly sure, that prior to touchscreens at least, any windows-based POS was way worse than plain old text-based interface that didn't use a mouse.

    I remember looking at the way it was in 1980ies, when at a medical lab I saw the people enter blood-sample test results into computer. No robots for blood test at that time, and no GUI for computer (a WANG minicomputer).

    They could really enter loads of results very quickly, because they only had a number of keyboard shortcuts to remember, like: test 621, patient 112, results 11.2 [enter] 7.5 [enter]

    Then they got upgraded to some windows-based soft several years later, and had to use mouse to move from entry field to entry field... the productivity went down by a mile.

    Any data entry software worth it's salt doesn't require you to move your hand from the keyboard to the mouse with any form of regular frequency. Just because someone forgot to implement the tab key in the new windows-based software doesn't mean that windows-based software in general was a step backwards for productivity.
  • (cs) in reply to Mr. Keith

    The elements for adverse possession are that the occupation has to be open, notorious, and hostile.

  • (cs) in reply to Mr. Keith
    Adverse possession would apply if this were land. If you notoriously occupy land without permission of the true owner for some period (16-21 years), you can have it retitled to you. (this has value in correcting for undetected surveyor or construction errors, or lousy recordkeeping, but otherwise is a pretty sucky common law doctrine).

    The elements for adverse possession are that the occupation has to be open, notorious, and hostile.

  • (cs) in reply to SkittlesAreYum

    Maybe not. If they total out their taxable items and declare tax on that as a whole for the period it probably works out fine legally. Plus it sounds like they get a small bonus from their sales tax holding account. No wonder they wanted that bug in the new system!

  • plasmab (unregistered)

    Facepalm.jpg

  • Reow (unregistered)

    I actually worked for a federal government department that asked me to do exactly what you are describing...

    I was replacing their existing (MS Access, user developed) 'solution' with an enterprise one that could be used nationwide. Amongst the 'features' of this application was a calculation to determine how many staff were required for deployment where. I found and fixed a slew of bugs in this calculation, then was informed that my results were "too correct" (i.e. didn't match the print-out from the old system). It took me longer to find and re-introduced every bug than to write the calculation in the first place (the bugs obviously hadn't been documented).

    I did, however, have the courtesy to isolate each in its own method called "Fudge<whatever>", so hopefully it will make fixing the issues easier for the poor bastards that picked up maintenance.

    Captcha: nulla. The IQ of those asking for the change.

Leave a comment on “Classic WTF: Faulty by Design”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article