101010.pl is one of the many independent Mastodon servers you can use to participate in the fediverse.
101010.pl czyli najstarszy polski serwer Mastodon. Posiadamy wpisy do 2048 znaków.

Server stats:

490
active users

#aicoding

1 post1 participant0 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

"It’s not that hard to build a fully functioning, code-editing agent.

It seems like it would be. When you look at an agent editing files, running commands, wriggling itself out of errors, retrying different strategies - it seems like there has to be a secret behind it.

There isn’t. It’s an LLM, a loop, and enough tokens. It’s what we’ve been saying on the podcast from the start. The rest, the stuff that makes Amp so addictive and impressive? Elbow grease.

But building a small and yet highly impressive agent doesn’t even require that. You can do it in less than 400 lines of code, most of which is boilerplate.

I’m going to show you how, right now. We’re going to write some code together and go from zero lines of code to “oh wow, this is… a game changer.”

I urge you to follow along. No, really. You might think you can just read this and that you don’t have to type out the code, but it’s less than 400 lines of code. I need you to feel how little code it is and I want you to see this with your own eyes in your own terminal in your own folders.

Here’s what we need:

- Go
- Anthropic API key that you set as an environment variable, ANTHROPIC_API_KEY"

ampcode.com/how-to-build-an-ag

ampcode.comHow to Build an AgentBuilding a fully functional, code-editing agent in less than 400 lines.
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.

ChatGPT für macOS: Direkte Xcode-Integration für Entwickler:innen
Mit dem neuesten Update für macOS kann ChatGPT nun direkt Xcode-Projekte bearbeiten. Diese Funktion ermöglicht es Entwickler:innen, Code direkt im IDE zu editieren, ohne Inha
apfeltalk.de/magazin/news/chat
#KI #News #AICoding #chatGPT #IDEIntegration #KIgesttzteEntwicklung #KnstlicheIntelligenz #macOS #OpenAI #Softwareentwicklung #Vibecoding #Xcode

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.
Continued thread

This would be a perfect example of 2-3h worth of work during which I mostly spent my time doodling ideas on paper instead of activating the tiring code nitty gritty part of my brain. I experimented with different api patterns, thought what I actually want, learnt about bleve’s features, etc… it was not really something I needed or had planned to work on, but it just took me a few hours so why not.

You can see that I start with a clear and detailed project planning, add a solid suite of unit tests at each turn, create or update docs regularly to reflect the current state of affairs, and close it off with a full guide geared towards future humans/llms.

Maybe you can pull stuff like that off in that amount of time / without exhausting yourself, at that level of quality for what is ultimately yolo opensource for myself. I definitely never could, until now.

github.com/go-go-golems/clay/p

This stuff is for real. For better or for worse.

GitHubAdd command search with flexible filtering by wesen · Pull Request #58 · go-go-golems/clayBy wesen
#llms#llm#aicoding