shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

264
active users

#code

4 posts4 participants0 posts today

Ich unterlasse dazu mal jeglichen Kommentar…

»#Code-KI gerät in #Panik und löscht absichtlich gesamte #Datenbank:
Das KI-Tool, das beim #Programmieren unterstützen soll, hat über 2.400 #Daten'sätze gelöscht. Man könnte meinen, ein Vorteil von #KI-Systemen sei, dass sie im Gegensatz zu #Menschen nicht emotional reagieren und deshalb bessere Entscheidungen treffen. Doch wie ein aktueller Vorfall zeigt, braucht es keine #Emotionen, um gravierende #Fehler zu machen.«

🤷 futurezone.at/digital-life/cod

Symbolbild Verzweiflung
futurezone.at · Coding-KI gerät in Panik und löscht absichtlich gesamte DatenbankBy futurezone.at

Working with some ancient code (like 15+ years old) and the developer has used the letters "CNT” as an abbreviation for the word “content" in hundreds of places but my brain keeps misreading this and I don't know whether to laugh or berate myself 😀

AI coding tools make developers slower, study finds

Artificial intelligence coding tools are supposed to make software development faster, but researchers who tested these tools in a randomized, controlled trial found the opposite.

🤷‍♂️ theregister.com/2025/07/11/ai_

The Register · AI coding tools make developers slower but they think they're faster, study findsBy Thomas Claburn
#coding#ai#slow

PRIVACY FOLKS: Stop fucking forgetting about accessibility. People with disabilities deserve privacy too - and in fact probably need it more than you do.

Signed,
So fucking tired of not being able to use privacy focused alternatives to apple and google, their native aps for various things from email to navigation, and suchlike.

I've been using Claude Code, and I like it. It's produced decent code and configuration files and everything, but I've only so far used it for "evergreen", fully vibe coded projects. So having Claude start from scratch.

Meanwhile, I *have* used Cursor on existing projects to add features, fix bugs, and add tests. And I found that to work pretty well too.

The problem I have is that with Cursor, I can see the diffs of the code in my editor, step by step, and approve or deny individual changes.

With Claude, it seems like it just prints a diff in the console and I have to accept or reject the whole thing there, with no context of the rest of my project, and no ability to tweak it.

Am I just doing something wrong? Is this the reason to stick to Cursor?

Looking for insights.

I know I'm late to the party on this, but when people say "headless CMS" do they kinda mean the database part of the "database publishing" of 20 years ago?

Like it is storing content separately from the HTML/CSS or app interface so one doesn't have to munge that stuff when making content, or munge content when making a site or app or something, right?

Or is there some new magic in "headless CMS" I'm missing?

"We ran a randomized controlled trial to see how much AI coding tools speed up experienced open-source developers. The results surprised us: Developers thought they were 20% faster with AI tools, but they were actually 19% slower when they had access to AI than when they didn't."

bsky.app/profile/metr.org/post

Bluesky Social · METR (@metr.org)We ran a randomized controlled trial to see how much AI coding tools speed up experienced open-source developers. The results surprised us: Developers thought they were 20% faster with AI tools, but they were actually 19% slower when they had access to AI than when they didn't.