3 ms·
Using a debugger on my own code is easy and I love it. The second the debugger steps deep into one of the libs or frameworks I'm using, I'm lost and I hate it.
by avhception 1y ago
Using a debugger on my own code is easy and I love it.
The second the debugger steps deep into one of the libs or frameworks I'm using, I'm lost and I hate it.
That framework / lib easily has many ten thousands of person-hours under it's belly, and I'm way out of my league.
- ronjakoi 1y agoBut you can just use the "step out" feature to get back out when you realise you've gone into a library function. Or "step over" when you can see you're about to go into one.
- avhception 1y agoWhile that's true, it doesn't necessarily help me understand why my parameters for said lib or whatever lead to things blowing up.
- never_inline 1y agoIDEs tend to have a "just my code" option.
- msluyter 1y ago"Step out" is how to get out of the lower level frameworks, and or "step over" to avoid diving into them in the first place. I can't speak for other IDEs, but all of the JetBrains products have these.