IceCream – Never use print() to debug again(github.com)
29 pointsby gregsadetsky17 hours ago9 comments
  • trvvan hour ago
    It's neat how trivial it is to do this in C, only takes a couple of macros. https://github.com/trvv/_/blob/d4899741c4f35833b8e86d16e2163...

    Looks like the project has a linked repo that appears to do a similar thing for C but it doesn't generically format the arguments.

  • oweiler12 hours ago
    Or use tests and/or a debugger. Which gives you all the listed benefits w/o an additional dependency.
    • ollysb2 hours ago
      Different tools for different cases. Debuggers are great for a snapshot in time but print statements are better for seeing the execution flow.
    • pjmlp11 hours ago
      Yeah, the amount of wasted hours with 1960's teletype debugging.

      Ah but servers and embedded, that is why telemetry, execution traces, and debugger controlled action points exist.

  • awoimbee9 hours ago
    Debugging in python is already so easy with `print(f"{myvar=}")` and `breakpoint()`...
    • Hackbraten7 hours ago
      This is the correct answer. `ic(foo(123))` can be written as `print(f'{foo(123)=}')` without depending on yet another third-party library which is not pulling its weight.
  • RockRobotRock11 hours ago
    >Do you ever use print() or log() to debug your code?

    I haven't written my own code in months at this point...kind of depressing to think about

    • benj11120 minutes ago
      So what do you actually do then?
    • squirrellous5 hours ago
      My first thought as well. Debugging is actually a decent use case of AI.
      • vitally36432 hours ago
        I have a board with a logic analyzer, debug/flash probe, PSU, and multimeter on my desk being driven and debugged all autonomously by the AI.

        While the automation and systems side of my brain is thrilled that all of this id automated and integrated, developer brain is sad

  • smackeyacky7 hours ago
    I haven’t used print for debugging for ages. Now it’s all trace on azure and hope your bug ends up in the sampled data in whatever that stupid thing is called. App insights or some rubbish. Apparently a good old log file just isn’t good enough it has to be larded up with a query language. Grep was fine guys.
  • Borborygymus8 hours ago
    Remember COBOL's EXHIBIT?
  • IshKebab4 hours ago
    ...use slightly fancier print() instead!
  • soizi10 hours ago
    why another tool for that ? think standard with other team/company and use the same integrated ones.
  • imagent7 hours ago
    [dead]