I can relate to that. Sometimes I just don't even add the print and just take a stab in the dark. And then again. And after couple attempts I just sigh and start using the tools and thinking about how to approach the problem and corner the bug. I don't think it's just laziness. It feels more like I am hesitant to add another "proper" task to my internal backlog. Also, you really should get yourself an USB to serial adapter. Just make sure to check the voltages.
This is why running the program with a debugger can be helpful. If you run into an error (e.g. exception, panic), the debugger will stop, tell you where it happened and allow you to do debug things. If your "stab in the dark" fixed it, it will run till completion and exit. Beats running the program, having it fail, and re-run the program with the debugger every time you make a change.
The quality of guests you get is amazing. Love the channel!
Resisting the urge to not mention obscure ladybird bugs
I can relate to that. Sometimes I just don't even add the print and just take a stab in the dark. And then again. And after couple attempts I just sigh and start using the tools and thinking about how to approach the problem and corner the bug. I don't think it's just laziness. It feels more like I am hesitant to add another "proper" task to my internal backlog. Also, you really should get yourself an USB to serial adapter. Just make sure to check the voltages.
This is why running the program with a debugger can be helpful. If you run into an error (e.g. exception, panic), the debugger will stop, tell you where it happened and allow you to do debug things. If your "stab in the dark" fixed it, it will run till completion and exit. Beats running the program, having it fail, and re-run the program with the debugger every time you make a change.
@@maleldil1 I rarely run into exceptions. And if I do, I usually fix it right away. Logic bugs are more insidious.
This guy is amazing humble 👏👏👏
this time it works, classic!