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 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 hehe... heck yes. Ruby puts, but with bracketing statements so they stand out in STDOUT...

puts '++++++ something weird is going on +++++'
puts "#{does_this_even_work?('foo')}"
puts '++++++++++++++++++++'

pry debugger when I can be arsed, but printing is still my 'goto' tool 😁

@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 I even use unsafePerformIO in Haskell so I can use print statements (shocking!)

@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)

Sign in to participate in the conversation
Computer Fairies

Computer Fairies is a Mastodon instance that aims to be as queer, friendly and furry as possible. We welcome all kinds of computer fairies!