Analyse von 11.805 Codierungssitzungen von 68 Entwicklern über 3 Monate.
Wichtigstes Ergebnis: 1,4 % der Zeit mit dem Debugger von VS Code. 75 % haben es nie genutzt.
Die meisten Debugging-Vorgänge erfolgen stattdessen über console.log() (wird angezeigt als "Erstellen" Und "Erkunden" in Daten).
Ich werde in den Kommentaren einen Link zur vollständigen Methodik hinzufügen.
Von Equivalent-Yak2407
7 Kommentare
Wow. I find the debugger so useful that I should be around 20 percent, I guess.
It’s true!
I don’t know why it’s so hard to use the debugger. Maybe something to do with configuring it.
I have used it a few times. And it was useful. But for some reason I don’t find myself going to it very often and every time I do I spend ages trying to remember how it works.
[deleted]
Meanwhile I’m here mostly using VSCode as an overengineered text editor.
Lot of code is written without test ability in mind. Thus the console log.
I love to step through my code in a debugger, but sometimes multi thread code is easy if we use logging and write another program to parse / analyze the logs.
candidly, never learned how to use it. I’m open to it, but it seems like a lot ofeffort to understand when console.log often works well enough? same with Python print statements
VSCode debugger isn’t great. Jetbrains products have much better debugger albeit taking more memory