I had a think about where I first learned to use a debugger. The combo of M$ making it easy for .NET and VB6 and working professionally and learning from others was key. Surprised it is less popular. Tests have made it less necessary perhaps BUT debugging a unit test is a killer move. You quickly get to the breakpoint and can tweak the scenario.

▲

NitpickLawyer 5 days ago | parent | next [-]

> I had a think about where I first learned to use a debugger

Is this not taught anymore? I started on borland C (the blue one, dos interface) and debugging was in the curriculum, 25+ years ago. Then moving to visual studio felt natural with the same concepts, even the same shortcuts mostly.

▲

giveita 5 days ago | parent [-]

Nothing useful I do in my job was taught by another person in a classroom.

▲

cluckindan 5 days ago | parent [-]

Clearly, you have been in the wrong classroom.

	▲	marssaxman 4 days ago \| parent \| next [-]
		A good number of us were never in any classroom, when it comes to the skills we use in our careers.
	▲	giveita 5 days ago \| parent \| prev [-]
		Or the wrong jobs!

▲

robertfw 4 days ago | parent | prev [-]

my development workflow with python often boils down to repeatedly running `pytest --ff --pdb -x`...

- run my tests, running any previous failures first - drop into the debugger when a test fails (or of course, hits a breakpoint) - end the test run after the first failure

use debugger to figure out what went wrong, fix it, wash, rinse, repeat