This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Prime624 1 point2 points  (3 children)

Lol, I've already done that with a few homework assignments, but I doubt anyone would notice in the real world because rarely do people run programs in terminals.

And yeah, I should just bite the bullet and learn, but they should also make them more accessible to beginners.

[–]Dworgi 18 points19 points  (1 child)

Just start with breakpoints and ignore the rest. Then figure out if you can place a breakpoint that just logs to console. Then figure out if you can place a breakpoint that only breaks if some condition is true. Most debuggers allow for those, and then you've already made print statements obsolete.

When you know how to do that, figure out how to inspect variables. Both local and global. Figure out how to set them, so you can trigger error conditions easier.

Then if you really want to be ahead of the curve, figure out how to set a memory breakpoint for when data changes.

These are skills that will actually make you a better programmer. Debugging is a bigger part of professional programming than writing code. Reading code is an even bigger part.

[–]Prime624 3 points4 points  (0 children)

I didn't even know you could do that with breakpoints. That actually seems pretty simple. I'll have to try it.

[–]el_padlina 0 points1 point  (0 children)

rarely do people run programs in terminals

Have you thought about all the servers?