Why athletes need a ‘quiet eye’
61–70 of 73 posts
Re: Why athletes need a ‘quiet eye’
#62When I was taking driver's ed as a teenager the instructor showed us a video that illustrated a driver's gaze from the first person as they drove using a small circle. The difference between a skilled, competent driver and a student was that the competent driver only fixated on things that were likely to matter. So mostly their gaze was on the vehicle in front of them, followed by any place that could hold moving obj…
Re: Why athletes need a ‘quiet eye’
#63When you look at training and coaching as being instead of correcting or perfecting skills and their signifiers, but as "how you learn to learn," in that domain, a quiet eye is not an objective, but rather an effect of building skills on top of a set of underlying attitudes. Goodhart's Law has been quoted a lot here recently, (re: measure becoming target and ceasing to be good measure), but it applies here. The more…
i guess humans also suffer from branching stalls.
Re: Why athletes need a ‘quiet eye’
#64Earlier quoted context omitted.
Your eyes should be scanning at all times. Those 'experienced' drivers have literal blind spots and are likely to enter a mental state akin to a sleep state.
Your advice is for an experienced driver who wants to become even better. The original commenter's scenario talked about novice vs. experienced. If you just tell a novice driver to scan everywhere, it's not actionable advice. Since, as was pointed out, they have not built a good filter yet. They'll end up being stressed out looking all over the place, when the simpler advice that driver's ed gives like "check these 3…
Sadly, sites like this are full of ignorant, unskilled, overconfident motorists who don't like correct advice.
Re: Why athletes need a ‘quiet eye’
#65Earlier quoted context omitted.
Your eyes should be scanning at all times. Those 'experienced' drivers have literal blind spots and are likely to enter a mental state akin to a sleep state.
So what you’re saying is, learn from those most likely to get into car accidents, rather than the least likely? https://article.images.consumerreports.org/prod/content/dam/...
Re: Why athletes need a ‘quiet eye’
#66Earlier quoted context omitted.
Your eyes should be scanning at all times. Those 'experienced' drivers have literal blind spots and are likely to enter a mental state akin to a sleep state.
That’s not really what allows people to drive safely. Without filters youd treat stationary objects with the same deference as moving ones.
Re: Why athletes need a ‘quiet eye’
#67When I was taking driver's ed as a teenager the instructor showed us a video that illustrated a driver's gaze from the first person as they drove using a small circle. The difference between a skilled, competent driver and a student was that the competent driver only fixated on things that were likely to matter. So mostly their gaze was on the vehicle in front of them, followed by any place that could hold moving obj…
Intriguing. A friend of mine just learnt how to drive very recently. He told me he was able to pick up driving much faster than an average person as he was able to apply the skill he developed in many years of playing Counter-Strike Global Offensive in driving: Instead of looking everywhere he would focus his attention on things that likely to matter and react to it like he was playing the first person shooter game.…
He may have picked up driving quickly not because of Counter Strike, but for the same reason he was capable of becoming a skilled Counter Strike player- some genetic or psychological advantage that is independent of anything else. He may just be better than the rest of us at filtering and focusing!
In contrast, I played a bit of counter strike in high school but I never got even remotely good at it. I just didn't have any knack for it. And while I am now a fairly skilled driver (no accidents in 16 years on the road!) I suspect those early years it was a matter of very good luck that I didn't get myself killed behind the wheel.
Re: Why athletes need a ‘quiet eye’
#68When I was taking driver's ed as a teenager the instructor showed us a video that illustrated a driver's gaze from the first person as they drove using a small circle. The difference between a skilled, competent driver and a student was that the competent driver only fixated on things that were likely to matter. So mostly their gaze was on the vehicle in front of them, followed by any place that could hold moving obj…
https://www.google.com/search?q=sipde
Scan, Identify, Predict, Decide, and Execute
Don't know if that correlates with 'quiet eye' but it does put emphasis on the eye being engaged in a specific activity (the scanning). Looking for what's out there, with the intention of knowing about it, versus just randomly looking around. Or worse blankly staring without focus.
Re: Why athletes need a ‘quiet eye’
#69When I was taking driver's ed as a teenager the instructor showed us a video that illustrated a driver's gaze from the first person as they drove using a small circle. The difference between a skilled, competent driver and a student was that the competent driver only fixated on things that were likely to matter. So mostly their gaze was on the vehicle in front of them, followed by any place that could hold moving obj…
Experience teaches you the noise to ignore. Same thing applies to all sorts of disciplines, even debugging or fixing a code. An experienced dev can look at a large code base and spot a bug or just from the structure of the code tell if it's "badly written" code. An experienced sysops can look at large streams of system log files and tell you what's wrong with the system because they can ignore the noise. Someone else…
Just because a system is running doesn't mean it's running well. Just because code is orderly in appearance doesn't mean it's effective at performing the desired task.
Perfection is the enemy of good.
Sometimes a shambling mess of spaghetti is that way because of a lot of underlying and tangentially-related issues with the operating environment. Code can be perfect looking yet fail because developer expectation of the compiler/toolchain and the underlying OS don't actually function as documented. Of course this can also lead to things being brittle when the underlying issues change. Experience is knowing when those issues are involved.