• Bob Beats (unregistered) in reply to Lockwood

    and Bust the Buster that's jumBustin' your Trace

  • (cs) in reply to qbolec

    I'm afraid it was bad phrased. there was a table with articles and I took on Article after the other in an "outer" loop than I have waste places and did another loop for all the waste places. So a loop within a loop that's at least somewhere in the O(n²) area. And yes I did a trip to the database in every loop. So that was a terrible idea. However it was just meant to be run once and so I did not care but with enough articles and waste places it has come to a near grinding halt. (So it took maybe 30 minutes) to run for a certain customer....

    It was simply brute force. But in the end it just turns out that with better use of informaton this could be cut down considerably. Still the code was written. So I wrote I'm guilty of writing it....

  • dtoader (unregistered)

    This whole nested mess could probably be easily converted so some very simple SQL.

  • Anonymous (unregistered) in reply to dtoader
    dtoader:
    This whole nested mess could probably be easily converted so some very simple SQL.
    This whole nested mess Is easily converted To simple SQL

    Since you were pretty close already, I took the liberty of converting your comment into a Haiku.

  • Wyrdo (unregistered) in reply to 3rd Ferguson
    3rd Ferguson:
    ...queries their queues...
    ...queries their queues...

    Hmm...

    A quarrelsome quest for questionable queries! A quotidian quagmire quickly makes quad-cores querulous. But quality code quashes quackery.

    Let's quit and quaff!

    /14 layers of queues?

    I guess that makes you V-for-Vendetta's cousin Q? Wait, wasn't he supposed to be omnipotent or something? I'm all confused now...

    -- Furry cows moo and decompress.

  • RedWizard (unregistered) in reply to ObiWayneKenobi
    ObiWayneKenobi:
    What I want to know is how do you make time to refactor code like this? Every job I have worked at has always kept us developers swamped with "new" work and we are never allocated time to go back and fix things as the rule is "There is ALWAYS something to do"

    My current job could do with a fair bit of code cleanup but there is no time allocated. Should I pretend to take longer on other assigned tasks and use that time to refactor some code or develop a proof of concept to demonstrate how some things can be done better than they are currently?

    One Dilbert Cartoon sums it up: http://www.dilbert.com/2011-02-03/

Leave a comment on “14 Layers Deep”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article