This trend on X reappears every couple of months: console.log is the best debugger!
While log lines are cool and definitely give great value for the time invested, the problem is that when beginners see this, they never really take the time to go further and actually learn to use the DevTools (speaking of web apps), which is something you must know to uncover more difficult bugs, memory hogs, or leaks.
It's not uncommon for someone with years of experience developing web apps to see the debugger for the first time.
Awesome topic. Learning the effective ways of debugging is crucial for any software engineer to level up and perform effectively in their job. We're not just paid to build stuff, but also to fire fight, quickly.
I find the tracing tools that you mentioned super helpful. We use Jaeger in my team. And, it's very useful to know where the bottlenecks are. Especially while debugging parallelism issue or database issues. Which are the worst!
I guess I was fortunate that my journey to learning Python included Replit's 100 Days of Code, which included a lesson on the debugger. I don't use it perhaps as much as I should but when I get stuck it has been invaluable
> What’s the debugger?
This trend on X reappears every couple of months: console.log is the best debugger!
While log lines are cool and definitely give great value for the time invested, the problem is that when beginners see this, they never really take the time to go further and actually learn to use the DevTools (speaking of web apps), which is something you must know to uncover more difficult bugs, memory hogs, or leaks.
It's not uncommon for someone with years of experience developing web apps to see the debugger for the first time.
I'm always surprised at that as I started writing code before the web existed and using a debugger was a common, core skill.
Awesome topic. Learning the effective ways of debugging is crucial for any software engineer to level up and perform effectively in their job. We're not just paid to build stuff, but also to fire fight, quickly.
I find the tracing tools that you mentioned super helpful. We use Jaeger in my team. And, it's very useful to know where the bottlenecks are. Especially while debugging parallelism issue or database issues. Which are the worst!
I guess I was fortunate that my journey to learning Python included Replit's 100 Days of Code, which included a lesson on the debugger. I don't use it perhaps as much as I should but when I get stuck it has been invaluable