• Mikina@programming.dev
    link
    fedilink
    arrow-up
    2
    ·
    1 day ago

    You do that inherently when you are writing the code. Every line you write has already had that focus, because you had to come up with it.

    That you should also not trust every line of the compiled assembly after you wrote the code, and check it lime by line, is an extremely stupid argument.

    Of course, you should get someone else, with a fresh/unbiased opinion to review your code too, but just the act of figuring out every line you write is in some sense a rewiev, that there is at least a plan or reason why it was written.

    AI just randomly generates code without thought or reason, and you have to check everything. Unlike assembly generated from code.

    • tatterdemalion@programming.dev
      link
      fedilink
      arrow-up
      1
      arrow-down
      1
      ·
      1 day ago

      That you should also not trust every line of the compiled assembly after you wrote the code, and check it lime by line, is an extremely stupid argument.

      I guess it’s good that no one is making that argument then.

      • tyler@programming.dev
        link
        fedilink
        arrow-up
        1
        arrow-down
        1
        ·
        1 day ago

        that is the argument linus is making… he is comparing a deterministic tool (a compiler that outputs the same assembly every time) to a non-deterministic tool and saying that they are the same type of tool. that require the same level of review, when they do not.

        • tatterdemalion@programming.dev
          link
          fedilink
          arrow-up
          1
          arrow-down
          1
          ·
          24 hours ago

          he is comparing a deterministic tool with a non-deterministic tool

          Yes, but that’s not the argument Mikina was stating. Linus was never advocating for reading assembly line by line. Linus was using that as a satirical example, not suggesting anyone should actually do that.