• (disco)

    Good thing that they have only one chart per page.

    EDIT: oh and SCEOND

  • (disco) in reply to Anonymous
    Anonymous:
    EDIT: oh and SCEOND

    nah. That's a FRIST.

    Paula doesn't count. :-D

  • (disco) in reply to accalia

    *cough* http://what.thedailywtf.com/t/wrongness/7743/5 5th.

  • (disco) in reply to accalia
    accalia:
    Anonymous:
    EDIT: oh and SCEOND

    nah. That's a FRIST.

    Paula doesn't count. :-D

    Oh yeah, it should be TIHRD.

    Opps, I think my PHP script broke.

  • (disco) in reply to aliceif

    yeah, but as i said Paula Bean doesn't count (same as all the other bots we have running around here)

  • (disco)

    So now we have a WTF squared. The IT company for not fixing the problem This company for creating a WFT hack to fix it.

    So the next guy/gal can post this "solution" as the WTF to TDWTF.

  • (disco) in reply to tdwtf

    It's the great circle of WTF.

    [image]
  • (disco)

    Did I miss a "To be continued..."?

  • (disco)

    "You're right Liss, why do we keep paying them.." This is the part I was worried about too. Why pay people who don't do the job?

    ". Okay, guess we're going to fix it ourselves. Did they tell you which file that was?" And here we have the reason the business keeps having the issue... IT keeps fixing sh-t that isn't their responsibility. From the business perspective, the software keeps getting workarounds/fixes, So no need to pressure the provider. Either a weak IT leader, or a business that doesn't respect IT (often the same thing)...

  • (disco)

    @Maciejasjmj, well dramatized. :clap: Take a bow.

  • (disco) in reply to huh
    huh:
    Either a weak IT leader

    Didn't the part where they spent most of the day playing CS didn't ring any bell?

  • (disco) in reply to Eldelshell
    Eldelshell:
    Didn't the part where they spent most of the day playing CS didn't ring any bell?

    Oh come on, that was clearly a team building exercise.

  • (disco) in reply to huh
    huh:
    IT keeps fixing sh-t that isn't their responsibility. From the business perspective, the software keeps getting workarounds/fixes, So no need to pressure the provider.

    Why not? After all, you're (I assume) paying them for support too. In this particular case, they were able to devise a workaround, next time it might turn out to be impossible. Besides, it's an unsupported kludge that might stop working any minute now.

    Hacking workarounds should be a "when everything else fails" solution. In this case, everything else failed.

  • (disco) in reply to Eldelshell
    Eldelshell:
    Did I miss a "To be continued..."?

    You want a Hanzo saga? Because that's how you get a Hanzo saga.

  • (disco) in reply to Onyx

    Lyle is better at lasertag than you!

  • (disco)

    This reminds me of when I fixed bugs in a vendor's REST library by implementing a proxy and modifying data in-flight so it wouldn't crash the client API written by the same vendor, who also happened to have like 95% marketshare and was generally not interested in fixing bugs or improving their software.

  • (disco) in reply to aliceif

    Until Bert kicks him off his mommy and daddy's modem.

  • (disco) in reply to aliceif
    aliceif:
    Lyle is better at lasertagCS than you!

    Because the bastard always plays terrorist and buys the fracking Krieg!


    Filed under: Yeah, I haven't played CS in ages

  • (disco)

    Steve clicked a few times, and brought up another file in Notepad. This time, a random jumble of letters and symbols squished into a single line was staring at them menacingly.

    "And it's encrypted. Curses, foiled again..."

    Or maybe Steve was actually looking at a Perl script?

  • (disco) in reply to Maciejasjmj

    No, just that at the end it seemed it would continue with the "Revenge of the IT nerds" or something.

  • (disco)

    So what's the point to have the script download all the images if it only uses the first one?

    So many WTFs...

  • (disco) in reply to Nipo

    To leave the system in a known state?

  • (disco) in reply to Yamikuronue
    Yamikuronue:
    To leave the system in a knownbroken state?

    FTF... No, hold on, those are equivalent in this case. Carry on.

  • (disco) in reply to Onyx

    Exactly. The user was supposed to see one picture, and the idea was to make that visible. The script butts in, downloads the image as well as all next images / pages, then sends the first one to the user and discards the rest. Now what happens when the user wants to see the next page?

  • (disco) in reply to Nipo

    They simply request a refresh of the report, download the previous n pages of images of the report, then display the next image. For each page. Every time.

  • (disco) in reply to Nipo

    Nothing, because the whole thing happens on export and not while viewing the report. The script goes through the whole report, picking out images, so there's no "going to the next page" to speak of.

    As to why it scrapes all images - I'll check the submission later, because I remember it made sense to me. I think it was related to having no stop condition other than the two error images in a row.

  • (disco) in reply to Maciejasjmj
    Maciejasjmj:
    You want a Hanzo saga? Because that's how you get a Hanzo saga.

    That's also how we got Mandatory Fun Day.

  • (disco) in reply to Nipo

    The report had more than one chart. Each chart was an <img> with the exact same URL, which served the charts in order and only once. When all the charts had been loaded, the URL just served up an error page.

    So when you preview the report it looks fine, but the next time you view it (after exporting the HTML) the charts are all broken images. The fix was to create a new session and generate that same report, save all the chart images and export the HTML, and then inject the images back into the HTML as static images instead of that stupid dynamic link. Then give that to the user.

  • (disco)

    Silly me, when they said they were going to look at the source code, I figured that meant they were going to actually fix the bug.

  • (disco) in reply to Zylon
    Zylon:
    Silly me, when they said they were going to look at the source code, I figured that meant they were going to actually fix the bug.

    You are assuming that they have access to the server side code. I have two words for you: Crystal Reports.

  • (disco) in reply to Zylon
    Zylon:
    Silly me, when they said they were going to look at the source code, I figured that meant they were going to actually fix the bug.

    "You don't want to know, really," said Melissa, "Okay, it's PHP, right? Maybe we can take a look at the code?"

    Steve clicked a few times, and brought up another file in Notepad. This time, a random jumble of letters and symbols squished into a single line was staring at them menacingly.

    "And it's encrypted."

    Also,

    Maciejasjmj:
    As to why it scrapes all images - I'll check the submission later, because I remember it made sense to me.

    actually I was wrong, I don't think there's a good explanation.

  • (disco)
    Bluecorp was their company's main IT solution provider – their software was incredibly buggy and **almost unusable**, but over time the employees got familiar with its quirks and **worked around most of the bugs**.

    That seems contradictory.

  • (disco) in reply to chubertdev

    Not quite. That's where the almost part is. Their I.T.s are great beast tamers.

  • (disco) in reply to huh
    Anonymous:
    Good thing that they have only one chart per page.

    It was plausible to me that 1.img was the first image on each page, 2.img was the second. Works fine until you get up to NaN images per page -- or some idiot glommed all of the pages into one entity like a report (or infini-scroll).

    huh:
    This is the part I was worried about too. Why pay people who don't do the job?

    Perhaps because the company didn't have the programmer bandwidth to re-engineer every piece of crap code they relied upon. Who cares if a few kids have a problem working with it? The customer's problem got solved, and the kids learned some valuable anti-patterns to use if they become highly-paid consultants (or to avoid if they get a real job).

  • (disco) in reply to chubertdev
    chubertdev:
    That seems contradictory.

    Not at all. Please allow me to put it into terms you can understand:

    The Patriots almost lost the Superbowl, but then Pete Carroll worked around New England's loser ways.

  • (disco) in reply to boomzilla

    What does this article have to do with being butthurt?

  • (disco) in reply to chubertdev
    chubertdev:
    What does this article have to do with being butthurt?

    I wouldn't know.

  • (disco) in reply to chubertdev
    chubertdev:
    What does this (...) have to do with

    You must be new here.

  • (disco) in reply to DCRoss
    DCRoss:
    That's also how we got Mandatory Fun Day.
    [image]

Leave a comment on “Wrongness”

Log In or post as a guest

Replying to comment #:

« Return to Article