> I do want to point out that print debugging has one critical feature that most step-based debuggers don’t have: you can see program state from multiple time s

> I do want to point out that print debugging has one critical feature that most step-based debuggers don’t have: you can see program state from multiple time steps all at once. At Google, we have time-traveling debuggers neatly integrated into our cloud IDE: You can step forwards and backwards, you can inspect variables for all the values they've had or will have until program termination, and you can also see all invocations of methods (along with their parameters) that have happened or will happen. I still use logging for debugging. Cool tech aside, I think what you really need, above everything else, is the fastest possible iteration cycles.