Live data from Hacker News

Coding with LLMs in the summer of 2025 – an update

antirez.com

71–80 of 434 posts

Re: Coding with LLMs in the summer of 2025 – an update

#71

Earlier quoted context omitted.

I find it even more sad when people come out of the woodwork on every LLM post to tell us that our positive experiences using LLMs are imagined and we just haven’t realized how bad they are yet.

We don't just tell you they were imagined, we can provide receipts. https://metr.org/blog/2025-07-10-early-2025-ai-experienced-o...

Cursor is an old way of using LLMs.

Not to mention in the study less than 1/2 have ever used it before the study.

Re: Coding with LLMs in the summer of 2025 – an update

#72
post #25

> Gemini 2.5 PRO | Claude Opus 4 Whether it's vibe coding, agentic coding, or copy pasting from the web interface to your editor, it's still sad to see the normalization of private (i.e., paid) LLM models. I like the progress that LLMs introduce and I see them as a powerful tool, but I cannot understand how programmers (whether complete nobodies or popular figures) dont mind adding a strong dependency on a third part…

Why do you see this as a strong dependency? The beauty of it is that you can change the model whenever you want. You can even just code yourself! This isn't some no-code stuff.

Re: Coding with LLMs in the summer of 2025 – an update

#73

Earlier quoted context omitted.

I find it even more sad when people come out of the woodwork on every LLM post to tell us that our positive experiences using LLMs are imagined and we just haven’t realized how bad they are yet.

Some people got into coding to code, rather than build things. If the AI is doing the coding then that is a threat to some people. I am not sure why, LLMs can be good and you can enjoy coding...those things are unrelated. The logic seems to be that if LLMs are good then coding is less fun, lol.

Software jobs pay more than artist jobs because coding builds things. You can still be a code artist on your own time. Nobody is stopping you from writing in assembler.

Re: Coding with LLMs in the summer of 2025 – an update

#74

My question on all of the “can’t work with big codebases” is how would a codebase that was designed for an LLM look like? Composed of many many small functions that can be composed together?

I found that it is beneficial to create more libraries. If I for example build a large integration to an API (basically a whole api client) I would in the past have it in the same repo but now I make it a standalone library.

Re: Coding with LLMs in the summer of 2025 – an update

#75

I currently use LLMs as a glorified Stack Overflow. If I want to start integrating an LLM like Gemini 2.5 PRO into my IDE (I use Visual Studio Code), whats the best way to do this? I don't want to use a platform like Cursor or Claude Code which takes me away from my IDE.

GitHub Copilot is pretty easy to try within VS Code

Re: Coding with LLMs in the summer of 2025 – an update

#76
post #25

> Gemini 2.5 PRO | Claude Opus 4 Whether it's vibe coding, agentic coding, or copy pasting from the web interface to your editor, it's still sad to see the normalization of private (i.e., paid) LLM models. I like the progress that LLMs introduce and I see them as a powerful tool, but I cannot understand how programmers (whether complete nobodies or popular figures) dont mind adding a strong dependency on a third part…

> Programming used to be (and still is, to a large extent) an activity that can be done with open and free tools.

Since when? It starts with computers, the main tool and it's architecture not being free and goes from there. Major compilers used to not be free. Major IDEs used to not be free. For most things there were decent and (sometimes) superior free alternatives. The same is true for LLMs.

> The excuse "but you earn six figures, what' $200/month to you?" doesn't really capture the issue here.

That "excuse" could exactly capture the issue. It does not, because you chose to make it a weirder issue. Just as before: You will be free to either not use LLMs, or use open-source LLMs, or use paid LLMs. Just as before in the many categories that pertain to programming. It all comes at a cost, that you might be willing to pay and somebody else is free to really does not care that much about.

Re: Coding with LLMs in the summer of 2025 – an update

#77

Earlier quoted context omitted.

Yeah it is also a bit of a shibboleth: vibes coding, when I'm productive for the 80% case with Claude code, is about the LLM cranking for 10-20min. I'm instructing & automating the LLM on how to do its own context management, vs artisanally making every little decision. Ex: Implementing a spec, responding to my review comments, adding wider unit tests, running a role play for usability testing, etc. The main time we…

Your strategy only works for some domains.

Totally

We do this ~daily for:

* Multitier webapps

* DevOps infrastructure: docker, aws, ci systems, shell scripts, ...

* Analytics & data processing

* AI investigations (logs, SIEMs, ..) * GPU kernels

* Compilers

* Docs

* Test amplification

* Spec writing

I think ~half the code happening by professional software engineers fits into these, or other vibes friendly domains. The stuff antirez does with databases seems close to what we do with compilers, GPU kernels, and infra.

We are still not happy with production-grade frontend side of coding, though by being strong on API-first design and keeping logic vs UI seperated, most of our UI code is friendly to headless.

Re: Coding with LLMs in the summer of 2025 – an update

#78
post #71

Earlier quoted context omitted.

We don't just tell you they were imagined, we can provide receipts. https://metr.org/blog/2025-07-10-early-2025-ai-experienced-o...

Cursor is an old way of using LLMs. Not to mention in the study less than 1/2 have ever used it before the study.

The AI tooling churn is so fast that by the time a study comes out people will be able to say "well they were using an older tool" no matter what tool that the study used.

Re: Coding with LLMs in the summer of 2025 – an update

#79
post #49

Earlier quoted context omitted.

If LLMs were actually useful, there would be no need to scream it everywhere. On the contrary: it would be a guarded secret.

posting a plain text description of your experience on a personal blog isn't exactly screaming. in the noise of the modern internet this would be read by nobody if it wasn't coming from one of the most well known open source software creators of all time. people who believe in open source don't believe that knowledge should be secret. i have released a lot of open source myself, but i wouldn't consider myself a "true…

If consumer "AI", and that includes programming tools, had real geopolitical implications it would be classified.

The "race against China" is a marketing trick to convince senators to pour billions into "AI". Here is who is financing the whole bubble to a large extent:

https://time.com/7280058/data-centers-tax-breaks-ai/

Re: Coding with LLMs in the summer of 2025 – an update

#80
post #71

Earlier quoted context omitted.

Cursor is an old way of using LLMs. Not to mention in the study less than 1/2 have ever used it before the study.

The AI tooling churn is so fast that by the time a study comes out people will be able to say "well they were using an older tool" no matter what tool that the study used .

It's the eternal future. "AI will soon be able to...".

There's an entire class of investment scammers that string along their marks, claiming that the big payoff is just around corner while they fleece the victim with the death of a thousand cuts.

Post reply on HN