• qprimed@lemmy.ml
    link
    fedilink
    English
    arrow-up
    69
    arrow-down
    2
    ·
    1 year ago

    because, sometimes, having your program vomit all over your console is the best way to remain focused on the problem.

    • charliespider@lemmy.world
      link
      fedilink
      arrow-up
      16
      ·
      1 year ago

      This is the reason for me. Sometimes I don’t want to step through the code and just want to scan through a giant list of output.

      • AeroLemming@lemm.ee
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        1 year ago

        Sometimes, I don’t know what’s wrong, I just know that something in a specific area or small set of variables isn’t working right. It’s a lot easier to notice anomalies by looking through a giant wall of print statements than by stepping through the program. “Oh, that value is supposed to be in the range [0,1), why is it 3.6857e74?”

    • ripcord@kbin.social
      link
      fedilink
      arrow-up
      9
      ·
      1 year ago

      Similarly, every once in a while I’ll throw warning messages (which I can’t ship) to encourage me to go back and finish that TODO instead of letting it linger.

    • MajorHavoc@lemmy.world
      link
      fedilink
      arrow-up
      5
      ·
      edit-2
      1 year ago

      Exactly. And there’s plenty of places where setting up a live debug stream is a massive PITA, and finding the log files is only a huge PITA.

      Edit: But I’ve been promised AI will do both soon, so I’ll stop stressing over it. /s