I’ve been a dev for 26 years. Am now a technical architect. I use these tools occasionally but 99% of the time I just use console logging. It’s quick and it’s simple and it does the job the vast majority of of the time.
LOL me too. I've been doing this since the late 90s. I've tried using all of the newer/more complex tools, and they definitely have their use cases, but console.log is certainly simpler.
@@AbdurrahmanHafez Oh yeah, definitely not saying they are useless the force suspense and force error ones are super-useful. I'm just not using most of the debugging tools all that often. Especially breakpoints and IDE debugging. I don't think I've ever used that.
Ironically, the more "senior" I get (20 years) the less I feel a need for these things. A few strategically placed console logs tend to be sufficient for most bugs. Impressive though!
almost 20 years web dev here as well. Rarely use these tools. As you said: a few well places console logs + a great designed system is all you need. if the code however is poorly designed, I can see the need for these tools to help understanding what the f is going on. I once redid an entire label-printing system, because everything was touching and changing global variables on all sorts of weird ways, making it completely impossible to understand what was going on. Maybe one of these debugging tools could have done a difference, but this was even back before nextjs or react was a thing. Maybe even before typescript was a thing, or in its infancy (8-9 years ago).
It's inspiring to see how experience can simplify your workflow! Ironically, as a newbie with 2 years of experience, I find that I often need to rely on all the new tools out there to be a good developer.
@@khairiyusoff5040 I think its because you get to a point where you know how the code is supposed to behave and know how to code around potential bottlenecks or problematic areas. Which also means that when you do run into bugs, your instincts tell you exactly where the problems might lie and all you need to do is to verify which one of them gives you the wrong data, needs a filter or what it is. But please use the tools you want to use that can help you not only fix the bugs but also learn whats going on “behind the scenes”. That, in my opinion, is one of the most valuable skills to have in this programming world. Knowing something as “simple” as why you cannot add two decimal point numbers together and then expect the result to be correct, or that most react components can and should be done without useEffect, because using useEffects will add several re-renders and you cannot expect the correct data from the get go, delaying everything below it. Essentially in React you are fighting against creating re-renders. There are instances where we actually go “around” some systems and get their data directly from cookie/storage on load, because otherwise we would have to wait on them spinning up first, delaying everything by several renders / miliseconds.
more senior dev type videos please, helps a lot to build intuition, learning right way to think and muscle memory for resolving stuff right from the beginning! Super helpful ❤❤❤❤❤
This is great- Im a senior dev (10 years), but the biggest challenge for debugging react apps now is the number of packages that use context to wrap around the parent component, and screws up normal rendering and react behavior. It can be really challenging to see what caused a re-render: css, context, props, hooks, etc. Then, using refs throughout adds another pile of complexity.
Amazing video. I always thought that react dev tools would be kind of hard to use and understand but this video has proved otherwise. Now I find them much easier to learn. thank you.
I have been following this "kid" for so long, but I'm only now starting to fully understand all his "black magic". Thank you for all your vids, even the ones I had to watch over and over, and even the ones I could never fully grasp. To all the OGs arguing that they know better because they have long-term experience that trumps modern gadgetry. You're right. Back in the day, we used to set up breaks, and have to manually parse through the code, variables, functions, and the like to see what was what, and what was breaking where. Remember, this is a new generation of coders who grew up with more precise tools. That being said, that's the main reason I have not been able to keep up with a great deal of this modernity. Sometimes a simple console.log does do the trick.
I just commented the same thought. I wonder if it's because with more experience our code tends to be less convoluted and also we have an overall better sense of where the problems likely lie.
Great job as always!!! I personally would have explained a bit more about the Profiler. There're indeed no really good resources about this tool on the web and having a real-time app analysis would be great and very instructive.
Very useful, I use these a lot, if you have a big project with tons of deep-nested components, without these tools it would take you a lot of time to debug, especially when working with Promise and API
Love this! BUT, here is some constructive feedback... Stop with the clickbait titles, and FOMO material to scare people to learn concepts. I have to always filter out so many parts of your messaging in my head to ensure I'm learning this because I want to vs. doing it because I'll be useless otherwise. Focus on more objective content, let your viewers decide the value of it and for you not to state what the industry is based on your personal opinion on how it should be. Your standard is way to high (which is why your content is good), but as I can see in the comments your statements around the industry are just not good for peoples minds. That said, no content like this online rn, so I'll keep watching you!
I've been successfully avoiding debugging tools and using console log (or variants) for over 30 years now :) Trust me, you get much more efficient with it than you think. (im not saying more than with debugging tools)
I was in a senior position and I'm now at a company where they don't have these imaginary roles. Call me "company fish" or whatever as long it pays fair according to my experience lol.
Brother can you suggest me linkedin social login library for React with Typescript which should be freeware and can be used in production. I tried many but none of them are working.
Thanks for the helpful video, Kyle. Awesome like always. In my Vite React app my source shows as "chunk-XYQJLCXN.js?v=2ca49224:41998" or other random characters instead of the actual file name. Why does this happen and how do i address it?
I’ve been a dev for 26 years. Am now a technical architect.
I use these tools occasionally but 99% of the time I just use console logging. It’s quick and it’s simple and it does the job the vast majority of of the time.
LOL me too. I've been doing this since the late 90s. I've tried using all of the newer/more complex tools, and they definitely have their use cases, but console.log is certainly simpler.
Thanks, I'm not alone!
I am a console logger too, but these tips sometime help and save some time
@@AbdurrahmanHafez Oh yeah, definitely not saying they are useless the force suspense and force error ones are super-useful. I'm just not using most of the debugging tools all that often. Especially breakpoints and IDE debugging. I don't think I've ever used that.
@@alexfoxleigh9443 as an architect your focus is probably on much more highlevel concepts than debugging individual react coponents 🙂
Ironically, the more "senior" I get (20 years) the less I feel a need for these things. A few strategically placed console logs tend to be sufficient for most bugs. Impressive though!
almost 20 years web dev here as well. Rarely use these tools. As you said: a few well places console logs + a great designed system is all you need. if the code however is poorly designed, I can see the need for these tools to help understanding what the f is going on. I once redid an entire label-printing system, because everything was touching and changing global variables on all sorts of weird ways, making it completely impossible to understand what was going on. Maybe one of these debugging tools could have done a difference, but this was even back before nextjs or react was a thing. Maybe even before typescript was a thing, or in its infancy (8-9 years ago).
It's inspiring to see how experience can simplify your workflow! Ironically, as a newbie with 2 years of experience, I find that I often need to rely on all the new tools out there to be a good developer.
@@khairiyusoff5040 I think its because you get to a point where you know how the code is supposed to behave and know how to code around potential bottlenecks or problematic areas. Which also means that when you do run into bugs, your instincts tell you exactly where the problems might lie and all you need to do is to verify which one of them gives you the wrong data, needs a filter or what it is.
But please use the tools you want to use that can help you not only fix the bugs but also learn whats going on “behind the scenes”. That, in my opinion, is one of the most valuable skills to have in this programming world. Knowing something as “simple” as why you cannot add two decimal point numbers together and then expect the result to be correct, or that most react components can and should be done without useEffect, because using useEffects will add several re-renders and you cannot expect the correct data from the get go, delaying everything below it. Essentially in React you are fighting against creating re-renders. There are instances where we actually go “around” some systems and get their data directly from cookie/storage on load, because otherwise we would have to wait on them spinning up first, delaying everything by several renders / miliseconds.
more senior dev type videos please, helps a lot to build intuition, learning right way to think and muscle memory for resolving stuff right from the beginning! Super helpful ❤❤❤❤❤
awesome, we need more senior developer type videos
I just wanna say thank you bro , been watching your vids during my days as practicing coding and finally got a junior dev position.
This is great- Im a senior dev (10 years), but the biggest challenge for debugging react apps now is the number of packages that use context to wrap around the parent component, and screws up normal rendering and react behavior. It can be really challenging to see what caused a re-render: css, context, props, hooks, etc. Then, using refs throughout adds another pile of complexity.
At last, a useful content without clickbait name. That's why I subscribed this channel initially. Good job!
😂😂
Amazing video. I always thought that react dev tools would be kind of hard to use and understand but this video has proved otherwise. Now I find them much easier to learn. thank you.
I have been following this "kid" for so long, but I'm only now starting to fully understand all his "black magic". Thank you for all your vids, even the ones I had to watch over and over, and even the ones I could never fully grasp.
To all the OGs arguing that they know better because they have long-term experience that trumps modern gadgetry. You're right. Back in the day, we used to set up breaks, and have to manually parse through the code, variables, functions, and the like to see what was what, and what was breaking where. Remember, this is a new generation of coders who grew up with more precise tools. That being said, that's the main reason I have not been able to keep up with a great deal of this modernity. Sometimes a simple console.log does do the trick.
I was using it many times, but i haven't known this tool have that much features.
Thank you for this video ❤
Oooooohhhhh yes you're a genius. I was searching for this kind of tutorial. Merci beaucoup ❤❤❤
what exactly is genous about using debugging tools
Probably the best actual teaching channel for JS devs besides Dave Gray or Kevin Powell the css master. Great job as always Kyle! Sub 4 life!
Great tips. Loving your videos from past 2 years. Always learns something new
I just commented the same thought. I wonder if it's because with more experience our code tends to be less convoluted and also we have an overall better sense of where the problems likely lie.
Great job as always!!! I personally would have explained a bit more about the Profiler. There're indeed no really good resources about this tool on the web and having a real-time app analysis would be great and very instructive.
Always I learn with yours videos, just the essential and simplify version, good job!!!
Thanks, this saved my career as a frontend engineer
Very useful, I use these a lot, if you have a big project with tons of deep-nested components, without these tools it would take you a lot of time to debug, especially when working with Promise and API
I never knew react dev tools were so useful!!!
thanks great video, would love to see videos about how react handles ui updates and more advanced behind the scene stuff
Love this! BUT, here is some constructive feedback... Stop with the clickbait titles, and FOMO material to scare people to learn concepts. I have to always filter out so many parts of your messaging in my head to ensure I'm learning this because I want to vs. doing it because I'll be useless otherwise. Focus on more objective content, let your viewers decide the value of it and for you not to state what the industry is based on your personal opinion on how it should be. Your standard is way to high (which is why your content is good), but as I can see in the comments your statements around the industry are just not good for peoples minds. That said, no content like this online rn, so I'll keep watching you!
I would love to see these tools on a more robust React app. Like in a more real-world setting
thanks great video, would love to see how react works in detail and why sometimes ui delegates
I couldn't see the connection between seniority and using dev tools. Great video though. Hope we will see more.
Senior dev here, never needed more than console logs in 3 years of tech leading
The tools he is explaining are for productive senior devs. not for the classic senior devs
@@vigikaranvijayaratnam7943 aww you’re cute
Priceless advices, each time. Thanks and congrats mate
a Ton of very useful information for getting into React debugging
Thanks man for this great tutorial!
Amazing tutorial Kyle! Thank you
A master class! Great tutorial!
Awesome! Thank you!
Thanks man, great walkthrough.
thanks a lot for all of your usefull toturials❤,please create react hook form toturial, guys please like this comments if you wnat it to
Nice job! What colorscheme did you use?
This was perfect thanks so much!
You're amazing! A big thanks from 🇧🇷
Too much knowledge thank youu
Nice, can you make this video with next JS 15 and turbopack? Please
Great stuff!
make sure to watch this video in 0.75 playback speed
Thanks
Do you plan on making svelte/sveltekit videos?
Overrated
more senior videos please
great video, thank
awesome content, thank u very much
Bro create Penpot plugins 🎉
Hi from Georgia🇬🇪 Can you show us your setup?👀💻🖥
Thanks alot
I could have used this video in 2021 when I contracted for Facebook and there was really zero help from management on debugging React
I've been successfully avoiding debugging tools and using console log (or variants) for over 30 years now :) Trust me, you get much more efficient with it than you think. (im not saying more than with debugging tools)
Thanks for sharing 👍
Let's always do alot of good ❤
Nam myoho renge kyo
Thanks 👍
thanks kyle
P.S. Why does strict mode render twice? Really asking...
Sounds like a click bait. No senior can avoid console log.
How do I debug the code inside of Canvas while developing 3D web/apps using Three.js, React-Three-Fiber...?
Great stuff
can I get any real time application of debugging video or example to large project ?
How can we achieve the REACT/NEXTJS debugging in webstorm IDE?
Junior, Senior, Manager are just payroll positions. It says nothing of your abilities to debug an app.
I was in a senior position and I'm now at a company where they don't have these imaginary roles. Call me "company fish" or whatever as long it pays fair according to my experience lol.
Typically a junior in any field has just started and a senior is someone who has a lot of experience. Kinda simple really.
Come on it is just the classification so we know the experience level, dont be so butthurt with the terms.
That was a click bait for new comers
What??? Then truck, car, motorcycle are just about fuel consumption. It says nothing about their carrying capacity 😂
Brother can you suggest me linkedin social login library for React with Typescript which should be freeware and can be used in production. I tried many but none of them are working.
Have you tried project idx?
Hi @kyle if possible could be little bit slow like what I feel is your speaking too fast so unable to follow you
why i use components tab , my shows : chunk.... in file name , does anyone have any idea what might be wrong
it is impossible to pay attention to code editor/web page while you keep bouncing your head on camera. seems those dog dolls to put over a car panel.
Does the nextjs debugger work for the app router?
u forgot to say sooner at the start "start building your dream projects SOONER" lol
awesome
React is a pain. Pain to use and debug.
This was helpful
my experience is that these tools have bugs sometimes😢.
Bro this head will fall off one day I tell you💀
4:11 u got me here😂😂 (only Indians will understand)
❤
Pro TIP: If you don't use REACT, you won't need to debug react.
Until next time 🏃
You got 1.5 million subs but the vids are 20k views with a bunch of ai spam in the comments, what up woth that
Stop shaking your head
Please stop shaking your head only!
Not that Vue js had vue devtools for months.... lol jk. All is Javascript in its core😊
bro i like you content but please stop moving your head .
Chat gpt can debug it faster and solve it as well
no, it cant
Panjabi head live
3 mins
low quality indian style videos as always
There is no senior ... It's scam 😂 you can work 40 years.. and can be junior 😆😆
Thanks for the helpful video, Kyle. Awesome like always. In my Vite React app my source shows as "chunk-XYQJLCXN.js?v=2ca49224:41998" or other random characters instead of the actual file name. Why does this happen and how do i address it?
Nah! Console.log is king!