My actual advice for debugging is to play 'Everything Has Changed' by TSwift on repeat

Just started video, not yet completed, but can say - 100% right - debugging is best skill as you said.

Great video! Unfortunately in some companies it's not allowed to input company code into ChatGPT or similar software

nobody talks about how painstakingly diffuclt it is to truly debug. you have no idea how much pain it is

I cant stop thinking about how amazing your advice and Taro is. Its unimaginably helpful. (Although tough to implement practically in this case so far but its still the best)

Yea brotha, your KZfaq channel is gonna blow up. Very high quality content here. Thanks

wow the production value of these videos has gone up dramatically. super sick!

Thanks for the video Rahul i love it ❤

I love debugging. It’s like being a detective or figuring out a puzzle

Would like to see a video explaining bottom up and top down debugging

Pretty well explained. ChatGPT might not always work due to two reasons: 1. Overall complexity is too much to explain it to an AI. 2. Its simply proprietary information. But other than that chatgpt can surely help to understand some basic flows. Like you could say the function executed like this, what could have possibly gone wrong

good advice

Not 100% relevant to debugging others' code, but when *writing* debuggable code: - Don't duplicate similar code (DRY), all relevant logic should run through a single bottleneck in functionality. A bug for a single thing should happen consistently, should expose itself fast, and should be fixed everywhere by only fixing it once. - Don't do declarative programming on complex things with many side-effects. Gratuitous declarative programming is a fast way to launder bugs with working code by mixing them all together on the same debug line-step (and a way to make it easy to gloss over using the wrong algorithms and data structures). - Break out code into multiple lines instead of having functions nested in functions (nested in ternaries, nested in linq calls, nested in linq calls). - Feel free to put temporary data into temporary variables. You get to describe it with a variable name (self-commenting code), a debugger step to see its value, and it'll be optimized away when the time comes to release build. - Asserts and defensive programming. And prefer static asserts when possible. These make stepping through code with the debugger (breakpoints, conditional breakpoints, watchlist, callstacks) an order of magnitude easier.

Are there some good books/tutorials/courses to learn the art of debugging ?

Solid

what was the step 1 before chat gpt?

I love you man

I'd be careful pasting in your companies code to chatgpt for interpretation. InfoSec at your company may not like that

Haha, I'm glad I saw the original thumbnail 😂