[arend321]

I do a ton of coding (codex) with a tts/stt wrapper. During walks, cycling, in the car. Not every task is suited to this style of interaction, but many are. Long form codex replies are condensed, code blocks are suppressed all in the name of making it work for tts feedback. So it works best on well defined projects with guardrails, where you know the agent can perform well.

[mattmanser]

This is extremely dangerous and you should stop doing it.

https://etsc.eu/tiny-proportion-of-drivers-understand-danger...

[MiloLeo]

Talking on the phone is extremely dangerous? What are your thoughts on talking with a passenger? Is that something that people ought to stop doing? Drive in silence. 100% focus?

Seems like an overreaction.

[mattmanser]

It's not my thoughts, it's simple facts.

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.

[MiloLeo]

In what way is talking on the phone a different cognitive load that talking to a passenger?

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.

[Quotable1]

One key factor you’re missing is attention.

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.

[hathawsh]

That's fantastic. I have long, winding trails near me also and one of these days I also want to start prompting a coding agent on my bike with a headset. Do you recommend any particular type of headset?

Edit: never mind, I see you already suggested the Shokz OpenComm2 in another comment. Thanks!

[dfgtyu65r]

This is so alien to me. Why not plug into the machine matrix when out in the great outdoors enjoying sublime nature? Why not!

[arend321]

It's not a replacement for being outdoors, connecting with nature. It replaces indoor desk bound office work.

[fragmede]

During cycling! Do you have a phone mount on your bike that you use while biking or is it all in-ear?

[arend321]

I have my phone in my pocket, no screen interaction is required. I use a headset (Shokz OpenComm2) with wind muff (when cycling). I made an Android app that listens for codex turn-complete or intermediate updates and plays them back to me. My answer is transcribed and pasted back to the relevant codex (tmux) session on the server (which I can select by voice) a tiny layer helps with things like /new, /plan, answer selection, etc.

[fragmede]

I'd love to hear more about it!

[arend321]

I'm still wondering if this is something the big AI companies will come out with tomorrow, if it has business potential (it's extremely niche I think) or if I should put it on GitHub and build a community around it. This is what the Android app looks like: https://imgur.com/a/qy8B2gt https://imgur.com/a/C0eTPyn

[cafebabbe]

... I cannot think of an activity less suitable for coding (except scuba diving)

I would die In minutes

[arend321]

Think long winding, quiet, dedicated cycling roads in forested areas and natural parks. Not busy roads shared with cars and lorries.

[VBprogrammer]

I can't honestly think of a case where this would be remotely useful. This goes somehow beyond vibe coding to vibe interaction, where the only feedback comes via the AI. I'd love to see a concrete example of this working practice.

[arend321]

I've been building out the Android app that works as the wrapper between codex and me this way. ADB debugging access over WireGuard. I ask to add a local wake phrase detection for the phrase "Hey codex" to start dictation. Codex tells me it thinks Vosk or OpenWakeWord might be a good fit, I voice select Vosk. Codex starts working. Codex deploys (updates) the app on my phone and restarts it and I hear the task complete response. I say "Hey Codex" to test and ask for some tuning/improvements, or move onto the next task. All while keeping my phone in my pocket.

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.