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:

246
active users

#aicoding

0 posts0 participants0 posts today

It's also time for me to jump on the bandwagon of AI coding. In the past, I was using Copilot, and it was rather bad experience, but not always.

If you'd have to choose one, what would you choose? Copilot, Cursor, Claude Code, something else?

I'm #nvim user, so using Cursor would require from me to change my editor, and I'm not sure if I'm ready for it.

Is there anything else I could use with nvim on flat subscription except for GH Copilot?

#ai#coding#aicoding

I'm not sure if there's a place for auto admin panels (active_admin in Ruby or kaffy in Elixir or the OG Django Admin) anymore given that LLMs can *easily* generate kick-ass and fully dedicated admin panels in minutes 🤔

I've built two pretty advanced admin panels for my Phoenix apps (so, still kinda niche tech stack) with little to no effort. Apart from regular CRUD stuff, I've got advanced features like syncing data with Stripe, or lately I built a mailing list sync with MailerLite in like 2 hours.

Given this experience I really don't see why I would need a solution like Kaffy (I used it initially in @justcrosspost and then rebuilt the whole admin panel in literally less than an hour with much better end result).

What are your thoughts on this topic? 👍🏻 or 👎🏻?

Replied in thread

@elementary tl;dr I support your objectives, and kudos on the goal, but I think you should monitor this new policy for unexpected negative outcomes. I take about 9k characters to explain why, but I’m not criticizing your intent.

While I am much more pragmatic about my stance on #aicoding this was previously a long-running issue of contention on the #StackExchange network that was never really effectively resolved outside of a few clearly egregious cases.

The triple-net is that when it comes to certain parts of software—think of the SCO copyright trials over header files from a few decades back—in many cases, obvious code will be, well…obvious. That “the simplest thing that could possibly work” was produced by an AI instead of a person is difficult to prove using existing tools, and false accusations of plagiarism have been a huge problem that has caused a number of people real #reputationalharm over the last couple of years.

That said, I don’t disagree with the stance that #vibecoding is not worth the pixels that it takes up on a screen. From a more pragmatic standpoint, though, it may be more useful to address the underlying principle that #plagiarism is unacceptable from a community standards or copyright perspective rather than making it a tool-specific policy issue.

I’m a firm believer that people have the right to run their community projects in whatever way best serves their community members. I’m only pointing out the pragmatic issues of setting forth a policy where the likelihood of false positives is quite high, and the level of pragmatic enforceability may be quite low. That is something that could lead to reputational harm to people and the project, or to community in-fighting down the road, when the real policy you’re promoting (as I understand it) is just a fundamental expectation of “original human contributions” to the project.

Because I work in #riskmanagement and #cybersecurity I see this a lot. This is an issue that comes up more often than you might think. Again, I fully support your objectives, but just wanted to offer an alternative viewpoint that your project might want to revisit down the road if the current policy doesn’t achieve the results that you’re hoping for.

In the meantime, I certainly wish you every possible success! You’re taking a #thoughtleadership stance on an important #AIgovernance policy issue that is important to society and to #FOSS right now. I think that’s terrific!

I assess the state of dev tools in the AI-assisted coding era: from AI plugins for common IDEs, to agentic IDEs, to cloud native AI tooling. As you might imagine, it's an incredibly crowded field of AI coding vendors. I'm not a professional dev, but for my various web projects I use a combo of VS Code + Copilot (I do want to try Google's one too), ChatGPT (I pay for the Pro version) and playing around with new apps like Bolt and Warp. How about you? thenewstack.io/ai-powered-codi #AIcoding

The New Stack · AI Coding Trends: Developer Tools To Watch in 2025We assess the state of dev tools in the AI-assisted coding era: from AI plugins for common IDEs, to agentic IDEs, to cloud native AI tooling.

Google has just launched Gemini Code Assist for individuals, a free AI-coding assistant offering *90 times* more code completions than GitHub Copilot. Reminiscent of when Google launched Gmail in 2004 offering one gigabyte of storage space — more than 100 times what Yahoo and Microsoft had at the time. thenewstack.io/google-ai-codin #AIcoding #aidevelopment tip @Techmeme

The New Stack · Google AI Coding Tool Now Free, With 90x Copilot’s OutputGoogle launches Gemini Code Assist for individuals, a free AI-coding assistant offering 90 times more code completions than GitHub Copilot.

My latest post on @TheNewStack: I talk to StackBlitz CEO Eric Simons about its recent hard pivot from CDE (Cloud Development Environment) to an AI coding tool called Bolt. 60-70% of Bolt's users are amateur developers — me included — but he also told me how pro devs are using the tool. thenewstack.io/how-developers- #AIcoding #developers

The New Stack · How Developers Are Using Bolt, a Fast Growing AI Coding ToolStackBlitz was a browser-based IDE, but it's now pivoted to an agentic IDE called Bolt. We talk to its CEO about how developers are using it.

"#SanFrancisco—At the Game Developers Conference Monday, Roblox rolled out a new set of #AI tools designed to let the company's millions of player-creators create usable game code and in-game 2D surfaces using nothing but simple text descriptions."

Are #Roblox’s new #AICoding and art tools the future of #GameDevelopment? | #GDC2023 #Games #GenerativeAI | Ars Technica
arstechnica.com/gaming/2023/03

Ars TechnicaAre Roblox’s new AI coding and art tools the future of game development?New initiative aims to take game development past "the hands of the skilled few."