• 0x4E4F@sh.itjust.worksOP
    link
    fedilink
    English
    arrow-up
    24
    arrow-down
    3
    ·
    2 months ago

    Yep, unrealistic expectations.

    Or “you need a 12th gen i7 to run this thing”… the thing is a glorified Avidemux.

    • UnderpantsWeevil@lemmy.world
      link
      fedilink
      English
      arrow-up
      26
      arrow-down
      1
      ·
      2 months ago

      Christ, if you could see the abysmal efficiency of business tier SQL code being churned out in the Lowest Bidder mines overseas…

      Using a few terrabytes of memory and a stack of processors as high as my knee so they can recreate Excel in a badly rendered .aspx page built in 2003.

      • fibojoly@sh.itjust.works
        link
        fedilink
        arrow-up
        7
        ·
        2 months ago

        We have a table with literally three columns. One is an id, another a filename and a third a path. Guess which one was picked as the primary key?

        Never seen something so stupid in 28 years of computing. Including my studies.

      • ugo@feddit.it
        link
        fedilink
        arrow-up
        2
        ·
        2 months ago

        As a dev, I had to fix an O( n! ) algorithm once because the outsourced developer that wrote it had no clue about anything. This algorithm was making database queries. To an on-device database, granted, so no network requests, but jesus christ man. I questioned the sanity of the world that time, and haven’t stopped since.

        • UnderpantsWeevil@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          2 months ago

          Oh yeah, I love people who stick SQL lookups in a For Loop. Even better, the coder who puts conditional if (but no then/else) clauses around a dozen raw text execution commands that fire in sequence. So you’re making six distinct lookups per iteration rather than answering your question in a single query and referencing the results from memory.

          Internal screaming