boost if you still use print statements as debug
@squirrel I should read up on Python's logging system (makes a quick skim, ooh, it's a built in feature)
@squirrel wait, is there another way???
@squirrel is everybody gonna laugh at me because I don't know any other way???
@squirrel Some of the best devs do this often. There's an intuition at play, I think, whether trace writes or debuggers will be most productive, and where to use either one
@squirrel a little classier than that... i use a logger piped to stdout. :p
@squirrel tbf my code is artist code... so it's bound to be awful (and I haven't coded in a while. I am not good. XD )

@squirrel meh ... but I'm getting better - now I use syslog for spam .. less work after I fixed it and less work after i recognize, that my fix introduced more bullshit then good so log level DEBUG gets another shot 😄

(No the last one was a joke - most time I'm a responsible developer who knows the pitfalls in the code he's fixing)

@squirrel yay, I'm not the only one! :3
@squirrel I was trying to do a Google sheets script and console.log wasn't working, so I had to set the value of nearby cells to get my print statement equivalent...