2 ms·
For 'shallow' bugs, printing / logging - solves problem 90% of time. Deeper bugs use the IDE, breakpoints and debugger, goto definition and call stack examinat
by malux85 10y ago
For 'shallow' bugs, printing / logging - solves problem 90% of time.
Deeper bugs use the IDE, breakpoints and debugger, goto definition and call stack examination solve the other 10%
Some tips for production: Put logging calls in at critical points -- e.g. initialisation of interfaces log input and output shapes (I work in mostly in vectors), DEBUG level logging, which is more verbose, can log the shape of incoming vectors to help with sanitation efforts.