You can. I just find it annoying / inconvenient to have to manually set a breakpoint, and navigate around to find all the variables that I’m looking for. Granted, in this simple case setting 1 breakpoint and looking at the variables in the debug panel is probably easiest & fastest. But as soon as you have multiple places in the code you’re interested in and multiple executions/calls of those code points then you have to 1) press a lot of buttons (resume, resume, resume, step, resume, …) and 2) keep the sequence of values that you’ve seen in mind instead of seeing it all laid out in front of you at once.
If a debugger could produce a kind of “flow diagram” that shows me how all the values that I’m interested in have changed during execution, then I would use that debugger. But then it probably wouldn’t be called a “debugger” any more but something more like an “on-demand runtime state flow visualizer” or so
This was a bit off-topic, but hopefully still of interest to those just getting started (or close) with development.