I'm writing a story for the BBC website explaining the computer programming concept of technical debt and the way in which AI coding can contribute to a legacy of errors buried inside applications.
Technical debt describes the hangover going for a quick fix in coding and programming can cause. Sooner or later errors triggered by technology shortcuts will surface and require fixing.
The meteoric rise of AI coding has added a real bite to the technical debt cocktail. Now anyone can ask AI to produce a program for them. But AI hallucinations and mistakes are erupting inside corporations. Is technical debt costing more than it’s worth?
I particularly want to hear from businesses that have used AI to produce code and then had to address problems caused by this. And I need to speak to people who can talk without jargon or acronyms.
Please note, this is a story for the BBC's global audience. It will not involve tech industry rivalries or software product pitches.
Technical debt describes the hangover going for a quick fix in coding and programming can cause. Sooner or later errors triggered by technology shortcuts will surface and require fixing.
The meteoric rise of AI coding has added a real bite to the technical debt cocktail. Now anyone can ask AI to produce a program for them. But AI hallucinations and mistakes are erupting inside corporations. Is technical debt costing more than it’s worth?
I particularly want to hear from businesses that have used AI to produce code and then had to address problems caused by this. And I need to speak to people who can talk without jargon or acronyms.
Please note, this is a story for the BBC's global audience. It will not involve tech industry rivalries or software product pitches.
