Not actively writing code causes real cognitive decline as neural pathways become inaccessible, not just a subjective feeling of 'brain drain'.

1:40the time [clears throat] this is out, you'll have seen my video, if you haven't, give it a watch on mental health and AI coding. And the brain drain of letting AI do it for you is not just fake. It's not just something that we all feel. It's quite simply by not doing those things in repetition and by not allowing our brain to understand these processes, your brain is actually

2:07letting those neural pathways go away or they're there those pathways are uh becoming inaccessible. So it's not just like a feeling of brain drain. By not being actively involved in an active participant in your code or the process by which things are doing things, your brain is in fact not using those skills anymore. >> Yeah. It's not braining. It's so funny. I know a lot of marketing around like

2:36brain training apps use the word neuroplasticity, but it's a real thing and it is uh one of those things where you you do need to use it otherwise you will lose it. I think it's kind of a tricky thing because there's the syntax of it which somebody tweeted the other day like will the name of this podcast become like something retro when the syntax doesn't necessarily matter all

3:00that much and forgetting like the syntax like like if you're doing a reduce what are the arguments to reduce callback knowing what those what that signature is I don't think is as important as actually understanding how this stuff works. And if you are, I know a lot of people are just kind of glazing over the code or don't necessarily care how it's happening. >> If you don't know how a request flows