>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
IceCream – Never use print() to debug again
11–20 of 24 posts
Re: IceCream – Never use print() to debug again
#12Re: IceCream – Never use print() to debug again
#13>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
My first thought as well. Debugging is actually a decent use case of AI.
While the automation and systems side of my brain is thrilled that all of this id automated and integrated, developer brain is sad
Re: IceCream – Never use print() to debug again
#14Or use tests and/or a debugger. Which gives you all the listed benefits w/o an additional dependency.
Re: IceCream – Never use print() to debug again
#15Looks like the project has a linked repo that appears to do a similar thing for C but it doesn't generically format the arguments.
Re: IceCream – Never use print() to debug again
#16>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
Re: IceCream – Never use print() to debug again
#17Re: IceCream – Never use print() to debug again
#18Re: IceCream – Never use print() to debug again
#19>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
Re: IceCream – Never use print() to debug again
#20Cannot recommend icecream, way too slow. But the use case of logging shines with realtime systems, or concurrent apps. You won't be able to efficiently debug them without logging. I live in my debugger, but logging is mandatory for the big picture.