@yakuplm: CLE300 4MATIC | lenkradmanufaktur.de #fy #viral #mercedes #nightdrive #inna

yakuplm
yakuplm
Open In TikTok:
Region: DE
Wednesday 22 July 2026 21:38:13 GMT
10487
581
0
55

Music

Download

Comments

There are no more comments for this video.
To see more videos from user @yakuplm, please go to the Tikwm homepage.

Other Videos

Your Brain Has Two Coding Modes (You re Using the Wrong One) Your brain has two ways of solving a coding problem, and programming trains you to use only one of them. You have been staring at the same failing test for three hours. You read the function line by line. You rewrote the assertion. You added logging, then removed it. Then you stand up for water, and somewhere between the desk and the kitchen the answer arrives fully formed. The kitchen did not solve your bug. Your brain solved it using a style of thinking you had been actively suppressing for three hours. In this video we look at what focused attention actually costs a programmer, why long stretches of hard focus make some solutions harder to find rather than easier, and why the breaks most developers take do not count as breaks at all. What we cover: Why reading code runs on the same limited working memory you use to hold a phone number The research suggesting your practical memory limit sits near four chunks, not seven What the default mode of brain function is, and what popular writing gets wrong about it Why setting a problem aside works, and the two conditions that decide whether it works The eye-tracking study showing expert chess players hunting for a better answer while their eyes never left the first one Why fixation never feels like fixation while it is happening Attention residue, task resumption, and why good programmers become fierce defenders of uninterrupted focus Four specific changes you can make on Monday morning The uncomfortable part arrives in the second half. Scrolling feels restful while behaving like work, and that distinction changes whether your brain solves anything while you are away from the keyboard. Studies referenced: Siegmund et al. (2014), Understanding understanding source code with functional magnetic resonance imaging, ICSE. Cowan (2001), The magical number 4 in short-term memory, Behavioral and Brain Sciences. Raichle et al. (2001), A default mode of brain function, PNAS. Sio and Ormerod (2009), Does incubation enhance problem solving? A meta-analytic review, Psychological Bulletin. Baird et al. (2012), Inspired by distraction, Psychological Science. Kounios and Beeman (2014), The cognitive neuroscience of insight, Annual Review of Psychology. Bilalić, McLeod and Gobet (2008), Why good thoughts block better ones, Cognition. Leroy (2009), Why is it so hard to do my work?, Organizational Behavior and Human Decision Processes. Parnin and Rugaber (2011), Resumption strategies for interrupted programming tasks, Software Quality Journal. Oakley (2014), A Mind for Numbers. Claxton (1997), Hare Brain, Tortoise Mind. Where do your best debugging breakthroughs usually happen? On a walk, in the shower, in the middle of a meeting? Tell me in the comments. Subscribe for more on what coding actually does to your mind. Chapters: 00:00​ Three hours on one bug 01:40​ What focused mode costs you 03:08​ The second mode 04:30​ The research on stepping away 06:48​ Why programmers get hit harder 09:25​ The reframe 11:07​ What to do differently 12:54​ Three takeaways This video is about cognitive science, not medical or psychological advice.
Your Brain Has Two Coding Modes (You re Using the Wrong One) Your brain has two ways of solving a coding problem, and programming trains you to use only one of them. You have been staring at the same failing test for three hours. You read the function line by line. You rewrote the assertion. You added logging, then removed it. Then you stand up for water, and somewhere between the desk and the kitchen the answer arrives fully formed. The kitchen did not solve your bug. Your brain solved it using a style of thinking you had been actively suppressing for three hours. In this video we look at what focused attention actually costs a programmer, why long stretches of hard focus make some solutions harder to find rather than easier, and why the breaks most developers take do not count as breaks at all. What we cover: Why reading code runs on the same limited working memory you use to hold a phone number The research suggesting your practical memory limit sits near four chunks, not seven What the default mode of brain function is, and what popular writing gets wrong about it Why setting a problem aside works, and the two conditions that decide whether it works The eye-tracking study showing expert chess players hunting for a better answer while their eyes never left the first one Why fixation never feels like fixation while it is happening Attention residue, task resumption, and why good programmers become fierce defenders of uninterrupted focus Four specific changes you can make on Monday morning The uncomfortable part arrives in the second half. Scrolling feels restful while behaving like work, and that distinction changes whether your brain solves anything while you are away from the keyboard. Studies referenced: Siegmund et al. (2014), Understanding understanding source code with functional magnetic resonance imaging, ICSE. Cowan (2001), The magical number 4 in short-term memory, Behavioral and Brain Sciences. Raichle et al. (2001), A default mode of brain function, PNAS. Sio and Ormerod (2009), Does incubation enhance problem solving? A meta-analytic review, Psychological Bulletin. Baird et al. (2012), Inspired by distraction, Psychological Science. Kounios and Beeman (2014), The cognitive neuroscience of insight, Annual Review of Psychology. Bilalić, McLeod and Gobet (2008), Why good thoughts block better ones, Cognition. Leroy (2009), Why is it so hard to do my work?, Organizational Behavior and Human Decision Processes. Parnin and Rugaber (2011), Resumption strategies for interrupted programming tasks, Software Quality Journal. Oakley (2014), A Mind for Numbers. Claxton (1997), Hare Brain, Tortoise Mind. Where do your best debugging breakthroughs usually happen? On a walk, in the shower, in the middle of a meeting? Tell me in the comments. Subscribe for more on what coding actually does to your mind. Chapters: 00:00​ Three hours on one bug 01:40​ What focused mode costs you 03:08​ The second mode 04:30​ The research on stepping away 06:48​ Why programmers get hit harder 09:25​ The reframe 11:07​ What to do differently 12:54​ Three takeaways This video is about cognitive science, not medical or psychological advice.

About