[1] https://www.theguardian.com/technology/gamesblog/2014/apr/07...
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.
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 might be fixated on the high cpu load when the issue is a bad device.
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.
So you learn to recognize the set of signage you're expecting in a given pattern, and you recognize where the likely spots are for surprises, or you remember to watch for heads in the cars along the side so you know if someone's about to open a door.
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.
The car in front of you is by far the greatest risk to your safety that you can control. the car in back is a large risk but you have minimal control.
It talked about novice vs. "skilled, competent" drivers, which suggests the latter meeting some threshold beyond just experience. (Making their behavior even more likely to be a demonstration of skill and safe technique.)
Sadly, sites like this are full of ignorant, unskilled, overconfident motorists who don't like correct advice.
https://article.images.consumerreports.org/prod/content/dam/...