4 ms·
> The influx of AI-generated code, an ever-evolving threat landscape, and the push for shorter release cycles can jeopardize code quality. All of these factors
by rglover 3y ago
> The influx of AI-generated code, an ever-evolving threat landscape, and the push for shorter release cycles can jeopardize code quality. All of these factors dictate the need for continuous and accurate code analysis to help development teams spot and fix code issues early on so they can consistently deliver readable, maintainable and secure code.
You know, I read stuff like this and I wonder if anybody has thought maybe those things jeopardizing code quality should be discouraged as opposed to adding yet-another-tool.
- alfalfasprout 3y agoSadly, it's like outsourcing. People only learn once it comes back to bite them. It'll typically be in the form of a major security breach or the codebase becoming so painful to work in that it affects the business.
- sb8244 3y agoI mean, once the cat is out of the bag you have to care for it. It can be discouraged, but people will still use it, so helping is still good. Plus it helps non AI use cases at same time
- jasonlotito 3y agoI mean, this isn't adding yet-another-tool. These inspections have existed for years inside of JetBrains IDEs. I feel like this is just an "encyclopedia of inspections." I don't see any other uses for it. They are just providing everything they are testing in the various tools they offer.
- manbash 3y agoI actually don't understand the "AI-generated code" excuse. Code analysis should be part of the pipeline regardless. It's not like people are perfect code developers.
- dmolony 3y agoI think what they mean is 'an influx of AI-generated code (which is frequently garbage)'