Survey Surfaces Rising Tide of Production Issues Traced Back to AI Code

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

A survey of 400 business and engineering executives finds 80% have traced a production incident, outage, or customer-impacting defect to code generated by artificial intelligence (AI) tools in the past 12 months. Conducted by Wakefield Research on behalf of Sauce Labs, a provider of an application testing platform, the survey finds 83% of respondents work for organizations where more than 10% of the code running in production environments has been generated using AI, with 28% now running more than a quarter of the code in their production environments using AI tools. A full 93% said they also receive reports on that code, but only 38% receive them regularly. A total of 89% also said they disclose to customers when code has been generated using AI, but only 27% said they do so consistently. A total of 70% said their organizations now spend more than $1 million annually on AI-assisted application development tools and platforms, with 41% spending $5 million or more. A total of 89% described the return on investment (ROI) in AI as either significantly positive (30%) or somewhat positive (59%). More than half (51%) expect fully autonomous testing and software deployment to be possible in either two (27%) or three years (24%), compared to 8% that believe it is achievable now. More than half (53%) said deploying AI too quickly is the greater risk than falling behind rivals, while conversely, 47% said falling behind is the greater risk. More than 91% also said software quality has either significantly improved (18%) or somewhat improved (73%) thanks to adoption of AI …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://devops.com/survey-surfaces-rising-tide-of-production-issues-traced-back-to-ai-code/
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.