How would you detect the
presence of bugs in this
scenario?
I would ask AI. "Did the last commit introduce any bugs or unintended consequences?". In fact I already use this prompt after every change I make manually. How would you make sure the LLM
isn't adding yet another
useless, redundant function to
the code base?
By asking AI. In fact, I already run a long "Can you refactor anything in this codebase to reduce redundancy, improve readability, performance or maintainability" pretty regularly.Please don't tell me that never happens-- I've had one just in the last week and I use both OpenAI and Anthropic foundation models.
In fact, I usually let multiple LLMs implement the same feature, and then I compare them. I even run my own arena in which I calculate Elo scores for LLMs from my perspective of which one implemented features better.
Having the ability to control code agents via voice would not take away my ability to do that. But I think in the future, that will become less and less necessary. If we look back at this conversation in five years, it will look very archaic, and we will be used to having superhuman AI do everything for us. In 10 years, it will sound like a strange idea that humans were once fiddling with code to improve the quality.
Something something taking the crafts and the man out of craftsmanship to just get it out the door as quickly as possible.
All jest aside I mostly agree with you but I'd tack on another 20 years for a total of 30.
Though in this technological jump I don't think people are as excited (understandably) as when the teletype came on scene. I too like the potential but dislike the whole discourse around it, the ethics involved and the way it's deployed. Such is life I suppose.