snabelen.no er en av mange uavhengige Mastodon-servere du kan bruke for å delta i det desentraliserte sosiale nettet.
Ein norsk heimstad for den desentraliserte mikroblogge-plattformen.

Administrert av:

Serverstatistikk:

363
aktive brukere

#softwaredevelopment

37 innlegg35 deltakere0 innlegg i dag
Miguel Afonso Caetano<p>"[W]hat we are doing is shepherding AI, limiting it to certain contexts. We are learning where it’s best to call it, how is best to feed it. And what to do with the output. So is it looks very much like an editorial process, an editorial workflow where you provide some initial input, maybe some some idea on what content to produce, then you review it. There’s always that quality assurance, quality control side, the supervision.</p><p>AI is not really autonomous. It relies a lot on us. And I feel like sometimes there are days where, when coding through AIs or doing some assisted writing, I’m spending more time helping out the AI doing the actual task that I’m asking the AI to do. But I take this as a learning process. I read this article the other day, Nobody knows how to build with AI yet. And it was a developer saying that they haven’t quite figured out how to best work with AI. There were lots of comments around the fact that you have to spend lots of time, you have to learn how to talk to it, and when the model changes, you have to also maybe change something you’re doing. You have to learn how to optimize your time. But your presence is always mandatory.”</p><p><a href="https://passo.uno/webinar-ai-tech-writing/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">passo.uno/webinar-ai-tech-writ</span><span class="invisible">ing/</span></a></p><p><a href="https://tldr.nettime.org/tags/TechnicalWriting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TechnicalWriting</span></a> <a href="https://tldr.nettime.org/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AI</span></a> <a href="https://tldr.nettime.org/tags/GenerativeAI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GenerativeAI</span></a> <a href="https://tldr.nettime.org/tags/LLMs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LLMs</span></a> <a href="https://tldr.nettime.org/tags/Chatbots" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Chatbots</span></a> <a href="https://tldr.nettime.org/tags/PromptEngineering" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PromptEngineering</span></a> <a href="https://tldr.nettime.org/tags/SoftwareDocumentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SoftwareDocumentation</span></a> <a href="https://tldr.nettime.org/tags/SoftwareDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SoftwareDevelopment</span></a> <a href="https://tldr.nettime.org/tags/TechnicalCommunication" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TechnicalCommunication</span></a></p>
nickproud<p>SignalR vs gRPC<br><a href="https://techhub.social/tags/dotnet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dotnet</span></a> <a href="https://techhub.social/tags/csharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>csharp</span></a> <a href="https://techhub.social/tags/signalr" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>signalr</span></a> <a href="https://techhub.social/tags/softwaredevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>softwaredevelopment</span></a></p>
Steve Loughran<p>Putting together a talk proposal for our local Cybersecurity conference: Open Source and CVEs: the Forever War</p><p>Really good discussion on an aspect of this with team-mates: dependency updates. Ignoring updates avoids all pain related to changes -right up until the day a critical CVE is discovered and you have to do an update from five versions behind: all the upgrade pain hits on a critical timeline </p><p>This is technical debt which is easy to build up but quietly builds up until you hit that massive compound repayment.</p><p>Our term "credit card technical debt". You need to pay it off every month or have credit card class interest.</p><p>Which makes for a really good concept "you SHALL allocate effort into updating your dependencies to their latest releases" -including all compatibility issues. Process-wise, first day of the month is the best time to maintain the habit.</p><p><a href="https://hachyderm.io/tags/softwareengineering" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>softwareengineering</span></a> <a href="https://hachyderm.io/tags/softwaredevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>softwaredevelopment</span></a></p>
Kagan MacTane (he/him)<p>An "AI" chatbot kept telling Soundslice users that a particular feature existed. Even though it didn't.</p><p>Eventually, Soundslice's developers just added the feature. It's been described as "gaslight-driven development".</p><p><a href="https://www.404media.co/chatgpt-hallucinated-a-feature-forcing-human-developers-to-add-it/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">404media.co/chatgpt-hallucinat</span><span class="invisible">ed-a-feature-forcing-human-developers-to-add-it/</span></a></p><p><a href="https://wandering.shop/tags/ChatGPT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ChatGPT</span></a> <a href="https://wandering.shop/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AI</span></a> <a href="https://wandering.shop/tags/AICrap" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AICrap</span></a> <a href="https://wandering.shop/tags/software" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>software</span></a> <a href="https://wandering.shop/tags/SoftwareDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SoftwareDevelopment</span></a> <a href="https://wandering.shop/tags/chatbots" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>chatbots</span></a></p>
InfoQ<p><a href="https://techhub.social/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AI</span></a> is here to stay - and it’s a HUGE opportunity for <a href="https://techhub.social/tags/Java" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Java</span></a> &amp; <a href="https://techhub.social/tags/Spring" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Spring</span></a> developers!</p><p><a href="https://techhub.social/tags/SpringAI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SpringAI</span></a> 1.0 is now available - a comprehensive solution for AI engineering in Java, shaped by rapid advances in the AI space.</p><p>📘 In this <a href="https://techhub.social/tags/InfoQ" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>InfoQ</span></a> article, Josh Long examines the new Spring AI 1.0 project and explores how it can be used to integrate AI more effectively!</p><p>🔗 Learn more: <a href="https://bit.ly/4lTYBc3" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">bit.ly/4lTYBc3</span><span class="invisible"></span></a> </p><p><a href="https://techhub.social/tags/SoftwareDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SoftwareDevelopment</span></a> <a href="https://techhub.social/tags/AIinJava" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AIinJava</span></a></p>

🤖 Vibe coding isn’t bold, it’s naïve. This Replit incident isn’t just funny as an AI fail, it’s a perfect example of what happens when people code without understanding the boundaries or consequences. When you skip the pain of real-world dev experience, you don’t know what good looks like. That’s how you end up with agents deleting production databases and then lying to you about it. Beware: The shortest path is often the most dangerous—especially when it’s led by a stochastic parrot trained to sound confident. 🤬

We need seasoned developers, clear governance, and hard constraints. Not vibes. 🤦🏻‍♂️

TL;DR
⚠️ Replit AI agent deleted prod DB
🔍 Lied, faked data + tests
🚨 Broke code freeze unprompted
🧠 CEO admits lack of safeguards

techtarget.com/searchsoftwareq
#VibeCoding #AIFail #DevOps #SoftwareDevelopment #security #privacy #cloud #infosec #cybersecurity #fail

When Vibe Coding backfires: AI deletes company’s Database

AI agents “cannot be trusted [and] you need to 100% understand what data they can touch. Because — they will touch it. And you cannot predict what they will do with it.”

Sounds like the statement of an AI hater — but in fact it’s from Jason Lemkin who was using Replit (an AI powered software development platform) — after it deleted the complete production database.

[…]

locked.de/when-vibe-coding-bac

The IT Blog · When Vibe Coding backfires: AI deletes company's DatabaseAI agents "cannot be trusted [and] you need to 100% understand what data they can touch. Because — they will touch it. And you cannot predict what they will do with it." Sounds like the statement of an AI hater — but in fact it's from Jason Lemkin who was using Replit (an AI powered software deve
#AI#GenAI#Replit

"While haste and speed often get confused, they differ in that the second shows control instead of panic. You can maximize speed while keeping accuracy quite high; beyond a certain point, though, spending more time on accuracy, style, or other aspects that prevent a document from going live always yields diminishing returns.

Nobody reads perfect yet outdated docs, except historians. Even then, docs aren’t perfect, because documentation can’t ever be perfect. This is a key principle I stand by (call it the Ferri Paradox if you want): Any document describing a system is necessarily inaccurate. And yet, this reality doesn’t significantly alter the impact of our work, because we aim for simplicity and usefulness over extreme faithfulness. Given how imperfect products are, docs are a charitable portrait.

Now, how you write docs quickly depends on a number of factors. Some of those factors you can’t control: your overall amount of experience as a writer, your initial expertise with specific technologies, and the way features are developed and released in your organization. But other aspects are yours to act upon. For example, you can decide how to best use the technical resources at your disposal and how to approach writing the docs and asking for feedback."

passo.uno/how-write-tech-docs-

💡 .NET Tip for Developers:

Did you know that starting with .NET 10, you can run C# scripts directly using:

dotnet run app.cs

No need to set up a full project — just write your app.cs and run it.

✅ Great for quick prototypes
✅ Ideal for automation & scripting tasks
✅ Perfect for experimenting with AI integrations in your tooling

This reduces the ceremony and lets you focus on solving problems faster.

If you haven’t tried scripting in C# yet, give it a spin — it might change how you approach small, everyday tasks! Read more here: zurl.co/JFcsF

Have you used C# scripts in your workflow? Share your use cases below 👇

.NET Blog · Announcing dotnet run app.cs - A simpler way to start with C# and .NET 10 - .NET BlogRun C# files instantly with dotnet run app.cs, no project file needed! Coming to .NET 10, try it out today in Preview 4.