I've found that I tend to not use the debugger with test driven development, an appropriate level of refactoring (so subroutines aren't that long), and decent coverage with tests.

I have used a lot of the debuggers out there, but I find most of them inadequate. Most of my work is module development, but debuggers want a script to run. I guess I could run a test script in the debugger, but if I have a nice test script, I already zero in on the problem pretty quickly. If I have to write a short script to isolate a problem, I find it pretty pointless to start up the debugger to run it.

If I need something else, I just use print() statements, or have some sort of conditional logging turned on.

The people have have tried to convince me to use one or another debugger are usually the sort that work on single scripts and modules from only CPAN (so they aren't debugging their own modules). I'm just not doing that sort of development, or looking for the same sort of errors they are. Your mileage may vary.

No matter what anyone says, however, do what works for you. Give other techniques a fair shot, but use what makes you productive. Different people will like different things.