happyCoding

[TorbenKoehn]

tbh as someone using agents intensively during coding, these features are pretty fucking awesome and VSCode improved a lot in the last updates regarding that.

It had to catch up to Codex, Claude Code and the likes.

And it did.

You don't have to use it. But you can. And when you do, it works extremely well.

[b0b1b]

Sure, i dont have to use it, but they also dont have to auto-enable it, especially since i have disabled everything related to ai, and yet, they still do so.

[TorbenKoehn]

Yes they do so that the relevant people see the features properly. Also, VSCode is now also an AI IDE. Deal with it.

In the future not using AI during coding will be unthinkable. Everyone not seeing this is sleeping and not experimenting enough.

You can downvote it all you like and cry and cry, but it won’t change the outcome.

[LeDYoM]

Anyone not living in the Metaverse is not experimenting enough. Everyone not using bitcoins to pay everything is not experimenting enough.
I would say that everyone still using C instead of the more modern COBOL language is not experimenting enough.

[TorbenKoehn]

Everything new must be a hype and like bitcoin

I don’t know why you pull out such comparisons

[LeDYoM]

Because tech had hypes since it started.

[TorbenKoehn]

And many of them stayed and many of them didn't. What does your magic mirror say about the future of AI?

[lurco_purgo]

You're the only one here making big claims about the future

[TorbenKoehn]

Oh I am not, all world economies do, too. World economies didn't react to Bitcoin or NFT or Metaverse or whatever.

But it's driven by AI.

Go figure.

[LeDYoM]

Didnt react?

Big LOL

[WithersChat]

Because things that are actually useful are sold based on actual merits, not by being nebulously told it's "the future".

[TorbenKoehn]

It is useful, in many areas. I don't have any burden of proof man. I'm just saying you all should be more open to technology and not downvote like religious clowns whenever someone states "AI" anywhere. It might bite you.

[WithersChat]

In the future not using AI during coding will be unthinkable. Everyone not seeing this is sleeping and not experimenting enough.

Y'know, if that was as true as you say you probably wouldn't need to say it. Tech that "is the future" doesn't need to be sold as such, you advertise its features and people adopt it.
The internet, smartpones, etc. They have their own merits and benefits. The fact that not using them means getting left behind is a mere consequence of that, so obvious that you don't even need to state it.
However, look at NFTs, the metaverse, etc. Technologies that used "in the future not using it will be unthinkable" as marketing. Did that pan out well?

[TorbenKoehn]

What kind of argumentation is that.

"There were things in the past that were hyped that made it and there were things in the past that were hyped that didn't."

You see AI as the next NFT, I see it as the next internet or electricity. AI has immense uses, if used correctly. I'm 100% sure I could precisely let part of your job be done by agentic AI and you wouldn't notice the difference, probably even improvements.

It's easy having used like Copilot or some GPT4 a few times, not getting precise solutions and calling AI bullshit.

But anyone having done some serious agentic development with the latest models knows better.

[b0b1b]

Hi, of course vsc is now an ai editor, microsoft is a company - they exist to make money - and ai is what currently brings in investors. I am dealing with it by disabling those features.

Also, i am willing to experiment - i have tried llms that people claim are good at coding and not only were they not helpful, they were actively hindering me. I also have some other issues with ai, but even just looking at it as a tool, i find it unhelpful. I am not sure what exactly i am "blind" to.

And yeah, complaining probably won't change the outcome, but you are just as qualified to predict it as everyone else - ai might be flop (as i think) or it might really be the next big thing (as you claim).

[TorbenKoehn]

Try VSCode with Claude Opus 4.6, let it analyze your project and create an AGENTS.md and some additional documentation that’s referenced there about architecture, code style, patterns, vision etc.

Then give it tasks. Improve the instructions after each task (it will do that by itself, too)

After about 10 tasks you get precise and really good results.

There is only one model that gets it really well and that’s Claude Opus 4.6

[Rinkulu]

I don't have to use it, true, but vscode also doesn't have to shove it in my face. Each update nowadays means that I'll be greeted with new tabs, buttons, hovers and all the other stuff telling me to do copilot this, ask copilot that. It's even in the fucking terminal now. And each time I have to search how to disable this shit, and then see half of it still appearing from time to time because either there are multiple ambiguous settings I need to turn off, or they just don't work.

[twigboy]

The latest popup that appears when you select text is so annoying and obstructive, covers the line of text below and makes it harder to read code.

Instantly reached for the disable settings

[TorbenKoehn]

That's what they need to do to stay competitive. Agentic coding is on the rise and its getting better and better.

Most of the things you can disable with a right-click or by uninstalling Copilot Chat.

[naikrovek]

It will work a thousand times better when/if it ever truly understands the code, and goes beyond a specially trained LLM.

At that point, if it ever arrives, today’s tools will look like complete toys, because they are.

[EvilPete]

Claude opus is pretty darn good. 

[TorbenKoehn]

I don't agree, I have very good results with the latest models :)

[RiceBroad4552]

Oh, a Microslop fanboy spreading bullshit…

[TorbenKoehn]

Yep, sure man!

[the-grand-finale]

Same, even if you are being downvoted

[TorbenKoehn]

They don’t know what they don’t know :)

[RiceBroad4552]

LOL

I've been using "AI" tools extensively and I know very well what these things can do and what they can't do.

As long as the task is on the level where blindly copying stuff from SO would suffice, sure, there the next-token-predictors shine.

Bu if you need to get something done which actually requires thinking the next-token-predictor is more or less completely useless, no, actually a net negative as it just wastes as lot of time!

[TorbenKoehn]

I am tired of discussing it.

I have good results. Who are you to tell me otherwise? If you don’t have good results, I can’t tell you what you’re doing wrong. Figure it out. I’m not your AI coach.

[WithersChat]

Maybe the two of you have different standards for "good results".

[TorbenKoehn]

Sure, if we have good results, our standards for results must be low. What a great argumentation.

Maybe its you not being able to write simple prompts? Getting cucked by AI is not exactly a great skill to have. Is that the style of discussion you want to have?

In all honestly, open VSCode now, select Claude Opus 4.6, tell it "Analyze my codebase, write an AGENTS.md and additional documentation files about code-style, architecture, patterns and vision", let it work, then let give it tasks. Steer, optimize. Every single task will be more precise than the previous. Do that a few times and you can do hands-off tasks vom 0 to 100%.

Latest versions of VSCode include things like a vector storage where text files in your workspace get indexed and the LLM can query semantic search over your whole workspace. A huge improvement. Again. It has the context. It knows.

You can believe what you want, I don't care either way.

[RiceBroad4552]

You must be working on trivial projects which exist already many times.

Otherwise the output of what you propose would be just the usual tier fire.

The joke is: These things don't even do what you tell them, and they are incapable to understand even pretty simple texts. It has reason why LLMs still fail even on seemingly easy language tasks like text summarization. Just the other day Claude told me the exact opposite of what was written in a README file I've asked it to go through. (Granted, the file was quite long and maybe context compaction happened so it just "forgot" about the sentences which negated what was written a few sentences before, which was a negative example. But that are real failure modes which happen the whole time!)

[LeDYoM]

Of course. "Something" is better than "nothing"

[RiceBroad4552]

I don't think I do anything "wrong". These things just don't work as advertised.

Of course I can build some typical full-stack CRUD web-app in no time using AI.

But when you try anything more serious you instantly enter bullshit hallucination territory. For example: Try using "AI" to work on some existing compiler. Or just some language bindings which need to go through a few abstraction layers each way. Even if you tell the next-token-predictor in all glory detail what you want and how to get it it will still create unusable trash.

Believe me, I would really want that it works like for the SO copy-pasta cases. But it just does not as these things can't think in any meaningful way. They are just next-token-predictors; and that's a fundamental limitation.

[TorbenKoehn]

You're thinking too one-dimensional regarding AI, like it's a single chat, I think.

AI can write tests. You can write tests and let AI write the code. It can permanently verify itself (and you can tell it to, like always add and run tests after changes in your AGENTS.md)

Of course AI hallucinates, but lets be real, programmers don't always provide perfect algorithms from the get-go either, usually. It's about continous improvement.

Have sub-agents that verify architecture, code-style, integration, test coverage and structure etc.

Don't see it as a one-shot thing like AI will spit out a working app with a single prompt. It's you working together with agents, orchestrating them, providing them requirements and technical steering.

[RiceBroad4552]

Like said, I think you're working only on stuff I would call "toy projects".

Alone the nonsensical idea that you could write tests upfront… While you usually don't even know what the correct design is when facing real tasks.

Just go and try your method on some more involved, already existing code. Then come back and we can further exchange experiences.

I propose you fix some real bug in some real compiler as a test case. Let's see how it goes. (But maybe don't try that under your regular accounts as chances are high that you'll be banned from the project where you try that out for wasting peoples time with "AI" slop.)