I have been troubleshooting this script for weeks and finally found it was trying to divide by zero.

  • raubarno@lemmy.ml
    link
    fedilink
    arrow-up
    5
    ·
    1 year ago

    Panicking on the error is much better than letting the system work continue on an undefined behaviour (good luck with debugging if you are ignoring all assertions)!

  • elouboub@kbin.social
    link
    fedilink
    arrow-up
    6
    arrow-down
    2
    ·
    1 year ago

    Makes me think of devs who debug with print statements instead of a debugger and breakpoints.

    • lens_r@kbin.social
      link
      fedilink
      arrow-up
      7
      ·
      1 year ago

      IMO there’s a place for both. A print statement will reveal a flaw in the programmer’s thinking regarding the control flow of the program and the state at that time. If a print statement gives something unexpected, you know exactly where to look in the debugger. If it gives you what you expected, it reveals the problem may be elsewhere

    • Fabiozeh@lemmy.world
      link
      fedilink
      arrow-up
      7
      ·
      1 year ago

      Well, Kernighan himself said “The most effective debugging tool is still careful thought, coupled with judiciously placed print statements.”

      If it was good enough for him…

    • ture@rational-racoon.de
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Worked on a project last year with one dev who was always super slow when having to debug even the simplest things. Turns out they didn’t know debuggers; just print statements… That person had more then 5 years of exp and was sold as a senior dev. But apparently nobody ever really coached them after uni and they never picked it up themselves :|