• TopRamenBinLaden@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      5 months ago

      I did well in data structures and algorithms in uni, but I have never had those topics come up in my 4 years of being a software developer. I’m in web development, FWIW.

      So you don’t really have to know that stuff, depending on what kind of software engineering that you get into.

      • kaffiene@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        5 months ago

        I’ve done Telephony, Games and I’m currently working in a high performance context. 99% of the time, you don’t need to be thinking about Big O

      • Buddahriffic@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        5 months ago

        Also big O analysis IMO should just be the starting point of maximizing efficiency. Those coefficients that just get dropped can have a huge impact. For example, any algorithm written in JavaScript or visual basic will be of the same order as that same algorithm written in C/C++ or rust, but will likely perform much slower. And the exact manner of implementation could even result in the C version being slower than the VB one.

        And on the other hand, I wouldn’t call a lot of big O analysis very advanced math. You might get a tighter bound with advanced math on some algorithms, but you can get a rough estimate just by multiplying and adding loops together. The harder question would be something like “does this early exit optimization result in an O(x³) algorithm becoming an O(log(x)*x²)?”

        • Zangoose@lemmy.one
          link
          fedilink
          arrow-up
          1
          ·
          5 months ago

          Another big thing that doesn’t get covered by big O analysis is the potential for parallelization and multi threading, because the difference created by multi threading only amounts to one of those dropped coefficients.

          And yet, especially for the workloads being run on a server with 32-128 cores, being able to run algorithms in parallel will make a huge difference to performance.

        • kaffiene@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          5 months ago

          I think the tldr; of what you said is that even when you have a theoretical handle on the growth function, you still need to actually benchmark anyway