4 ms·
There are a lot of contexts where debugging isn’t feasible, like rubbing your (flaky) test 600 times to figure out why it is failing 2 out of 600 runs. Since st
by seanmcdirmid 4y ago
There are a lot of contexts where debugging isn’t feasible, like rubbing your (flaky) test 600 times to figure out why it is failing 2 out of 600 runs. Since starting my job at Google a couple of years ago, I haven’t used a debugger once, it wouldn’t really work for what I’m doing. Couple that with remote development limitations (and not being able to run an emulator truly locally), and it doesn’t make sense to use a debugger even when it might be useful.