home.social

#aidrivendevelopment — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #aidrivendevelopment, aggregated by home.social.

fetched live
  1. Vulnerabilities Surge as Velocity Gap Widens in AI-Driven Development

    The alarming truth: while alert volume grew by 52% year-over-year, prioritized critical risks exploded by nearly 400% in just 90 days, leaving defenders scrambling to keep up with a tsunami of high-impact problems. A new dataset from OX Security reveals this velocity gap in AI-driven development,…

    osintsights.com/vulnerabilitie

    #AidrivenDevelopment #EmergingThreats #VulnerabilityManagement #ThreatIntelligence #PrioritizedRisk

  2. OpenClaw Troubleshooting: 'No Reply from Agent,' WORKFLOW_AUTO.md, and Silent Delivery Failures After deploying OpenClaw and documenting 16 incidents in one day , I kept getting questions a...

    #aidrivendevelopment #openclaw #guide

    Origin | Interest | Match
  3. With everyone investing in #ai, I am going to give my opinion on the subject and my predictions on the future.

    Disclaimer: I am a CS student, not an industry professional yet.

    I think it is very likely that #aiDrivenDevelopment will become a thing.

    However, the thing that is currently holding it back, is the ai will sometimes "hallucinate" and do things wrong. In addition, ai code tends to be less secure, not unlike just copying code from #stackOverflow without checking it.

    However, I imagine those problems will be lessened overtime, as it wasn't all that long ago that ai generated hilarious and garbled stuff from prompts.

    I think prompt engineering might end up becoming a core part of cs courses.

    I think the most similar example I can think of this development is the development of high level #programming languages, such as #python.

    Everyone knows python and #java are much slower than #c, #c++, or #rust. However, it is often quicker (and thus cheaper) to write in python when speed does not matter.

  4. With everyone investing in #ai, I am going to give my opinion on the subject and my predictions on the future.

    Disclaimer: I am a CS student, not an industry professional yet.

    I think it is very likely that #aiDrivenDevelopment will become a thing.

    However, the thing that is currently holding it back, is the ai will sometimes "hallucinate" and do things wrong. In addition, ai code tends to be less secure, not unlike just copying code from #stackOverflow without checking it.

    However, I imagine those problems will be lessened overtime, as it wasn't all that long ago that ai generated hilarious and garbled stuff from prompts.

    I think prompt engineering might end up becoming a core part of cs courses.

    I think the most similar example I can think of this development is the development of high level #programming languages, such as #python.

    Everyone knows python and #java are much slower than #c, #c++, or #rust. However, it is often quicker (and thus cheaper) to write in python when speed does not matter.

  5. @dekkzz76 @micahflee

    I don't know about that. From a simple economics view point, typically if something, in this case, #aiDrivenDevelopment saves money, money will be invested into it.

  6. @micahflee

    #aiDrivenDevelopment is a fascinating paradigm shift. I can definitely see it being more revolutionary than #LSP. I just hope that large language models get efficient enough to run sufficiently on consumer hardware (either that, or have an #APU (#AI processing unit) become part of our computers).

    I am not scared about AI, but I am scared of having a #Microsoft situation, where the only viable IDE's are closed source.

    Hopefully we can get something like LSP and be able to bring this functionality to #Vim and #emacs, as I will always argue that those are better than any IDE out there.

  7. @micahflee

    #aiDrivenDevelopment is a fascinating paradigm shift. I can definitely see it being more revolutionary than #LSP. I just hope that large language models get efficient enough to run sufficiently on consumer hardware (either that, or have an #APU (#AI processing unit) become part of our computers).

    I am not scared about AI, but I am scared of having a #Microsoft situation, where the only viable IDE's are closed source.

    Hopefully we can get something like LSP and be able to bring this functionality to #Vim and #emacs, as I will always argue that those are better than any IDE out there.