• TheCPUWizard (unregistered)

    Please note, there are two distinct types of internships [in the USA]... paid and unpaid.... For the former, the person is compensated at a fair market rate, and can perform actual work. For the later, the person is prohibited from performing any activity which would otherwise be performed by an employee. Unfortunately this is quite often violated, and the interns are not well enough informed as to their rights.

  • (nodebb)

    Still probably better than having 80% of your Devs/QA all offshore

  • (nodebb)

    I wish I had an intern who could hold four layers of abstraction in his/her head. One one my predecessors (the main architect apparently), in a world full of screws, only knew how to use a hammer.

  • Sauron (unregistered)

    it's good for the company building its network of professional relationships and recruiting opportunities.

    The companies that treat their interns as underpaid slaves probably don't really intend to actually recruit employees (let alone paying them decently). They're probably more the kind of companies that love doing mass-layoffs.

  • (nodebb)

    Oh boy, what language is that? Such a messy naming scheme...

  • WTFGuy (unregistered)

    We need to grant a little room for the code sample being anonymized. So the BusinessObject probably isn't, and maybe, just maybe, neither are ListA - ListD.

    But clearly this is the work of somebody who can just barely program. That's the WTF. And the business processes that let the kid loose unsupervised.

  • Extern (unregistered)

    Maybe this intern was smarter than we think, and objectId can differ from STRUCTURAL_UNIT for each BusinessObject. If you do not have a suitable dictionary (instead of listB) then those loops seem reasonable.

  • (nodebb) in reply to Extern

    I think the same, but to me the first step would be to build a suitable dictionary to avoid getting in an O(n²) join.

  • (nodebb)

    This organization has interns in its management, which explains everything.

  • (nodebb)

    "If all you have is a three-headed hammer, everything looks like three nails." — Me.

  • (nodebb)

    I wonder if different BusinessObjects can share the same objectId? In which case, this starts to look like a misguided attempt at sorting, or at least grouping, by objectId first.

  • (nodebb)

    Maybe that intern was smarter than we think, and this entire smoke screen was just a BS no-op they wrote to make it look like they were working hard, under the nose of a PHB.

  • codr (unregistered)

    What this code does is make a list of copies of BusinessObjects that are STRUCTURAL_UNITs. The naming is crap but this code isn't that bad. n-squared complex is not an issue if there aren't many objects. All we're doing is comparing integers. Why the copies? Maybe there's a mutation up ahead that shouldn't be changing the original objects. Maybe the result is passed off as a result and there's no guarantee as to what might happen to these objects down the line. Assist from the terrible names, this code just isn't that bad. I assume this code is marked as a WTF because of the comparison with the list generated from list A, as mentioned in the article. But the comparison is between objectID and STRUCTURAL_UNIT ID. They aren't the same thing. ListC only contains those BOs that are referenced by any STRUCTURAL_UNIT.

  • (nodebb)


    Addendum 2024-02-29 14:26: Recently, I stumbled upon an exceptional essay writing service based in Australia. This website caters specifically to the academic OZ Essay needs of students in the region, offering a local touch to essay composition. With a team of native English-speaking writers, it ensures a nuanced and culturally relevant approach to crafting top-notch essays.

Leave a comment on “Loop the Loop the Loop”

Log In or post as a guest

Replying to comment #:

« Return to Article