https://etsc.eu/tiny-proportion-of-drivers-understand-danger...
Seems like an overreaction.
All the studies show it's not an over-reaction, you're 400% more likely to have an accident. It is extremely dangerous and it's not an over-reaction, the more people do this, the more people die. It's simple maths. If you're doing extended programming sessions, you're not paying attention to the road like you should be.
And no, talking to a passenger is not as dangerous as it's a different cognitive load.
It'll take you 20 seconds to google this, please do and stop putting everyone else in jeopardy.
After googling the 8th or 10th result had a link to the study I assume you are referencing.
I just don't agree with you. I believe that there is risk when driving inherently although relatively low and a 400% increase from 0.0001 to 0.0004 does not really concern me.
I have been in one accident in 15 years and I was not at fault and it was unavoidable.
Many people engage in all sorts of distracted driving, texting, eating, driving while tired etc. which I would wager are more detrimental than speaking on the phone.
Having your one bone to pick being speaking on the phone just seems absurd and an odd message to preach when nearly everyone does it.
The difference between talking to a passenger versus using a hands-free phone is an interesting one. While they intuitively feel similar, it has been shown that speaking on the phone results in significantly worse performance. This is because a passenger shares awareness of the driving situation and surroundings. Their conversation naturally adapts to traffic conditions, often pausing or shifting topics to focus on the road, which can help with awareness.
Texting and eating are far more dangerous as they divert eyes from the road and introduce motor interference. Fatigue also severely degrades both attention and cognitive function.
Coding while driving does seem unnecessarily risky though. Unlike other non-motor distractions, it demands more cognitive engagement without necessarily moving your hands or eyes. It is far more demanding than a standard phone conversation, which has already been shown to impair driving.
You will make errors that you won’t remember because your brain is occupied with the code rather than monitoring the environment.
Your ability to recognize objects and react slows down. If a child runs into the road, that split-second delay could mean the difference between stopping or killing them. The same applies to sudden obstacles like kangaroos in my case. The delay in reaction could turn a near-miss into a fatal crash.
Most of the risk lies in the complex and unexpected situations. It's really not worth it, just listen to some music or an audiobook and enjoy your ride. Do coding later.
If you have any other psychology or cognitive-related questions to it I can try and answer. I'm not an expert in this specific area but we did some work on it at university.
Edit: never mind, I see you already suggested the Shokz OpenComm2 in another comment. Thanks!
I would die In minutes
But there are countless projects I work on this way. Eg, I got an email from person X, it says it encountered a bug when doing x and y. Codex reads the email (using nvidia/gliner-PII to hide PII data) and investigates the reason for the bug and proposes a solution. I ask it to implement the fix on my dev server and increase test coverage. I enjoy my walk and after say 7 minutes get a an overview of the fix and can decide to deploy to production.