This isn't at all surprising or unexpected, but it is concerning. We're giving development teams tools that dramatically increase their velocity, but we aren't maturing the rest of the software lifecycle at the same pace. The data is pretty clear: AI-generated code is directly contributing to more instability and security incidents in production. This isn't really a failure of AI; it's a failure of process. The stubborn organizational divide between development and security teams means we're accelerating into a wall.
TL;DR
🚀 Devs are using AI to code faster than ever, and productivity is way up.
📉 But this speed is linked directly to more software instability and production failures. One report states that 72% of organizations have experienced production incidents resulting from AI code.
🚧 The real bottleneck is automation for testing and security, which is lagging far behind.
🤝 It highlights an old problem: Dev and Sec teams are still not aligned, and AI is just amplifying the consequences of that disconnect.
https://www.techtarget.com/searchsoftwarequality/news/366632374/Market-research-AI-coding-tools-push-production-problems
#DevSecOps #AI #SoftwareDevelopment #Cybersecurity #security #privacy #cloud #infosec #agile #DevLive
It is the "I do not test on older devices but my web developer has the newest multicore multigig machine but I do not test on older hardware .... beeecause I can analyze the performance of my animation-overloaded website by measuring their CPU temperature" mindset.
It's a shithole based on perspective.
*innocent configuration oversight*
"If all those misconfigured systems were attempting to back up their data into my S3 bucket, why not just let them do so? I opened my bucket for public writes and collected over 10GB of data within less than 30 seconds. Of course, I can’t disclose whose data it was. But it left me amazed at how an innocent configuration oversight could lead to a dangerous data leak!"
This is so infuriating. Not only that devs use some magic packets with default configuration and produce data loss, but also that the managers require the devs to produce results asap. That's how such mess happens. #devlive #agile #rapid #prototype
Get ready for session 5 of the One Week Crunchless Challenge https://twitch.tv/timkrief