News: 1693942390

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

AI coding is 'inescapable' and here to stay, says GitLab

(2023/09/05)


Almost a quarter of organizations are already using AI to augment human software development, and over two-thirds of them are planning to use such systems, according to a survey from GitLab.

"If there was one inescapable takeaway from the survey data, it’s that AI in software development is here to stay," the code-hosting biz said in its [1]2023 Global DevSecOps report , where "global" means 38 percent of the 1,001 survey respondents hailed from the US, 37 percent hailed from India, and 63 percent identified as male.

"The vast majority (83 percent) of respondents agreed that it is essential to implement AI in their software development processes to avoid falling behind, and this was consistent regardless of respondents’ functional area (development, operations, and security), job level, or years of experience."

[2]

GitLab's report suggests AI adoption thus far has gone well, with 90 percent of those using machine-learning tools today saying they feel confident using them in their daily work. Others characterized their organizations' efforts integrating AI into the software development lifecycle as "very" or "extremely" successful.

[3]

[4]

The use of AI among respondents, however, is not all robo-generated coding. The top use cases were: natural-language chatbots in documentation (41 percent), automated test generation (41 percent), summaries of code changes (39 percent), tracking machine learning model experiments (38 percent), suggestions for who can review code changes (37 percent), and summaries of issue comments (37 percent).

Only then did code generation and code suggestions (36 percent) come up. So generating code isn't the primary use of the technology, which perhaps isn't surprising given that devs only spend 25 percent of their time writing code, according to the report.

[5]

The rest of their time consists of improving existing code (17 percent), meetings and administrative tasks (17 percent), trying to understand what code does (14 percent), testing (11 percent), maintenance (9 percent), and identifying and mitigating security flaws (7 percent).

[6]One third wiped off value of GitLab shares, Wall Street didn't like weaker outlook

[7]Tech job bonfire rages on as Microsoft, GitLab and others join in

[8]GitLab deploys on a Friday and ... is down for a few hours

[9]What it takes to keep an enterprise 'Frankenkernel' alive

About a third of survey respondents were "very" or "extremely" concerned about AI in the software development lifecycle, with about half of those (48 percent) worrying that AI-generated code isn't subject to copyright protection and about 39 percent fretting that generated code may introduce security vulnerabilities.

These DevSecOps practitioners also wondered whether AI will take their jobs. "More than half (57 percent) of respondents said they think AI will replace their role within the next five years," the report says.

Then there were some who anticipate that AI will generate work for them: "40 percent of security professionals said they were concerned that AI-powered code generation will add more to their plate, compared to just 29 percent of respondents overall."

One area where most seemed to agree is training: 81 percent of respondents said they need more training to use AI in the workplace and 87 percent said organizations will have to train employees to adapt to the new regime.

[10]

The report concludes by noting that respondents with more AI experience were less likely to associate AI with productivity gains and faster cycle times.

"AI may be able to generate code more quickly than a human developer, but a human team member needs to verify that the AI-generated code is free of errors, security vulnerabilities, or copyright issues before it goes to production," the report concludes.

DevSecOps today, ChatBotChaperones tomorrow. ®

Get our [11]Tech Resources



[1] https://about.gitlab.com/developer-survey/

[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/devops&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2ZPelAYD4kp@FpBt45W0NGAAAANM&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0

[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/devops&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ZPelAYD4kp@FpBt45W0NGAAAANM&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/devops&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33ZPelAYD4kp@FpBt45W0NGAAAANM&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/devops&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ZPelAYD4kp@FpBt45W0NGAAAANM&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[6] https://www.theregister.com/2023/03/14/gitlab_q4_2023/

[7] https://www.theregister.com/2023/02/10/tech_job_cuts_gitlab_microsoft/

[8] https://www.theregister.com/2023/07/07/gitlab_outage/

[9] https://www.theregister.com/2023/06/30/enterprise_distro_feature_devconf/

[10] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/devops&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33ZPelAYD4kp@FpBt45W0NGAAAANM&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[11] https://whitepapers.theregister.com/



What measure is over-confidence?

that one in the corner

> The report concludes by noting that respondents with more AI experience were less likely to associate AI with productivity gains and faster cycle times.

So we are left with a large pool of people without "AI experience"[1] who are being naively optimistic during the development phases (including code review etc as outlined in the article).

I was going to make snide comments about entrusting testing decisions to the AI, then, hey, at least they are doing *some* testing!

Say, are there are any stats about how long after deployment the major CVEs start to appear? Are we expecting a few house of cards to come falling down in 6 months? A year? Two?

[1] and, btw, no solid definition of what "AI experience" means - someone who has run Stable Diffusion at home? Or has followed some tutorials on training a simple Neural Net? Or has a research degree in AI from 2020 which only really covered NNs? Or has been involved since the 1980s and has a broad grasp on different AI models?

Significantly less jobs by 2040.

badflorist

In 17 years 9/10 programming jobs will have been replaced with "good enough" AI. 9/10 complaints about loosing a job will be AI generated. Have you recently enrolled in a college for "IT Security"? You might want to think twice because that particular field is about to be drenched in AI "solutions" as it's very scripty' to begin with.

Anonymous Coward

As far as natural language documentation goes, I have found CoPilot to be eager, but not accurate. But it would certainly pass any word count metrics, if that were the criteria.

It's great for predicting the next line or two, sometimes more. Sometimes it produces something that a little editing will fix.

In the Red Corner, Rust; in the Blue Corner, AI coders

Anonymous Coward

One believes it will free up programmer time and energy by removing the need to worry about the small details, allowing you to concentrate on the Big Picture of your code.

The other believes it will free up programmer time and energy by removing the need to worry about the small details, allowing you to concentrate on the Big Picture of your code.

One is missing a clear specification of how it works, the other is missing a clear specification of how it works.

One releases new features into the wild and sees which will stick with the devs using it, the other - umm.

One - oh, heck.

Why on earth do people buy old bottles of wine when they can get a
fresh one for a quarter of the price?