Cursor is effective at making 90-95% of code changes, my only input being phrases like:
"change <foo> to work like <bar>"
"add an argument in <foo> to do <blah>"
"add assertions in <foo> that make sense"
("that make sense" isn't an abbreviation)
My physical contact during these operations is typically clicking files to open, highlighting text, accepting or rejecting changes, and making manual edits whenever I get frustrated with trying to explain things to the AI.
This is a big change over how I wrote code 5 years ago. It also seems like a temporary workflow that's bound to change.
This market resolves YES if at the end of 2025, I no longer physically touch my computer while editing code and instead only use spoken natural language.
I won't bet.
@AriZerner You can interpret the market as being about whether I do it or not (it's already in fact technically possible today, just impractical). Sorry for the ambiguity.