I think maybe the reason I don't like debuggers (the kind you type commands into) is that it feels like an execution challenge, where I have to perform the correct sequence of commands and actions to get the information I want. With print statement debugging I just write more code and if it's not good enough I fix it.
So basically I want a debugger I can program ahead of time.
@madewokherd debugging is one area I live for full fat IDEs. Let me set a breakpoint, trace execution step by step, inspect full object hierarchy of everything currently in memory, etc
Follow
@directhex I seem to wind up predominantly in situations where IDE debugging isn't practical, or I probably would use them more.
@directhex Not sure how I'd feel about them if they were more frequently practical. I suspect I'd have the same basic problem with them, but actions would be easier to perform so it wouldn't bother me quite as often.