A while I ago I got one of those fancy split keyboards that's fully programmable. I ended up on the Ultimate Hacking Keyboard and spent quite some money & time on painstakingly setting up all the hotkeys to how they felt most natural to me.
Why did I do that?
Because I wanted to reduce the friction between whats in my mind & what's in my computer.
The more I can reduce not necessarily time, but friction in the process of getting my thoughts into the machine, the more I can stay in the thinking part, continue thoughts, keep flow.
The value I bring is not that I can type out code that someone gives me, and not even necessarily that I can come up with certain specific code, but that I can come up with a high level solution that solves the problem following certain constraints & requirements. Yes that often already includes most parts of the implementation & even specific coding styles; but it's still different from the typing process.
Active Exploratie Coding
I acknowledge there's a style of coding, where you're more so writing the code as you think; scrap parts again, etc. to help you explore the problem or solution space.
Ultimately, this is often just using the ability of our brain to self observe other parts of it's own output through different senses.
The effect is similar if you active-explore code, or if you talk your plan through (with the AI). With the benefit of a shared knowledge base after.
That's why rubber ducking is a thing.
It doesn't matter if you're setting up a million keyboard macros, have hard coded python scripts to automate your development process, or if an Agent is generating that code.
There's no moral in writing code.
As long as it does meet your requirements.