boost if you still use print statements as debug
And loggers, which you leave in the product when you ship it, so you can keep collecting that info
And then everyone secretly uses print statements all the time because you can just kind of drop them in with no setup
@squirrel i usually bind it to a function called p() so i can type it really fast lol
@squirrel hehe... heck yes. Ruby puts, but with bracketing statements so they stand out in STDOUT...
puts '++++++ something weird is going on +++++'
pry debugger when I can be arsed, but printing is still my 'goto' tool 😁
@squirrel a little classier than that... i use a logger piped to stdout. :p
@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)