Abdu

@RickStrahl Try opus 4.6. Give it examples and edge cases and tell it to go in a loop testing them and to have them all working. The more of them the better. Use a cli and yolo mode. This might go through a good amount of tokens.

Honestly I don't know how people get things to work with AI Agents. Most (and I mean MOST) of the time I try to build something I get the basics working great, but if there are complex edge cases, solutions fail to get even close to completion or to where the work can be fixed up and completed manually. Example: Today I've been fighting CoPilot with Claude (and GPT 5.4) for half a day now trying to build a custom Code/Textmate syntax that combines several languages and it just goes in circles. One syntax works, the other embedded syntax breaks. Fixes are applied, then the other works and the first one breaks. Now to be clear this is the kind of thing I would never tackle on my own (hideously complex RegEx expressions), so I can't even fix what's generated after, and I'm stuck here letting the agent do its thing. Agents are good at identifying and planning and reviewing, and I've fixed up and tweaked the plan uncountable times, started from scratch several times with updated initial plans and updated instructions from the previous workarounds, and then drilled deeper and deeper a few times, only to end up at the same failed result again and again. End result: I'm better off using the built in Handlebars support which does a better job with my custom syntax than what was custom built. Plus god know how many credits and energy was wasted for all that. Thing is that this is not unusual for what I've used this stuff for. And the tooling doesn't matter much - CoPilot, Codex and Claude CLIs it's all very similar in result. My success rate has got to be somewhere around 1:10. I've had a few big wins, but they are very rare. Most of the time I end up doing as I think I have to do here: throw out everything and go back to what I started with. And it's a monumental waste of time! I don't claim to be an expert by any means, but I think I have a pretty decent grasp on how to plan and prompt by now, and when to start over and how to tweak plans - but even with that the results are pretty disappointing given all the hype that I see. Is that just me, or is all the hype just that?

@burkeholland In the future, the 1M context will work like today's 100k. I am guessing this will happen with newer models. So keep experimenting until you know we reached the effective 1M context.

I keep trying to tell people this. The context window is not a memory. It’s a room. The more stuff you put in there, the more cluttered it gets until eventually the model just stays confused. Don’t listen to me. Listen to Matt.

@mkristensen The lack of workspaces in Visual Studio makes me use Copilot in VS Code

What features or extensions make you jump from Visual Studio to other IDEs and editors to perform certain tasks?

@mkristensen I would like to see something like VS Code's workspaces so that Copilot and agents can work across different repos. Instead of creating a temporary solution.

Both custom agents and skills will be supported in an upcoming update to Visual Studio. I'm playing around with it now in an internal build. Great stuff!

@jasonfried Interesting that they bothered to do that because almost no one looks down there in the pedal area, and notices the rubber detail.

Like most car pedals, the Porsche 928 clutch petal has grippy rubber tread. But back in the late 70s they just had more fun. They didn't have to embed "928" into the tread itself, but, then again, maybe they did. When you're that deep into a project, pride pops out all over the place. Are any mass production car brands having this kind of fun anymore?

@adamwathan Things you can pivot to. An AI service like Lovable, but it specialises in producing highly polished UI components using Tailwind. Video tutorials on Tailwind based UI components.

🎧 Recorded a new morning walk this morning, hard one to share because I'm sure people will want to roast me for it but have been transparent up until now so publishing it anyways.

@theo_albers @RickStrahl @mkristensen @VisualStudio There are options to save and load configurations in the installer. I haven't used them. I assume it's maybe for it to know your previous workloads. Anyway this is all to save a few clicks once every like 4 years!?

Hey @mkristensen - it'd be nice if there was an easier way to upgrade install a new version of @visualstudio. I had preview 2026 and release 2022 installed. Going to 2026 release I ended up doing 3 'installs' - uninstall 2022 and 2026 insiders and then install 2026. It'd be nice if on either of those first two, there was at least an option to upgrade directly to 2026 release. On another machine I opted to just stay with Insider builds until I run into a problem 😀.

@slashdot Good. Everyone wondered how kuiper is pronounced

Amazon Renames 'Project Kuiper' Satellite Internet Venture To 'Leo' ift.tt/RLoptzQ

@jasonfried As a customer I like roadmaps. It gets me excited to know what's coming. I know they're promises and I don't plan now for all of them to happen. It's ok.

I've never liked roadmaps. Even though they're for new things later, they've always feel like looking backwards in time. Essentially, it's a list that says "here's what we thought then". I prefer working from a "here's what we think now" position. So every few weeks we decide, from scratch, what's worth working on next. Old ideas are fair game if they're as good as the new ones today. But writing them down before doesn't give them any priority over ones we come up with on the spot today. Here's more about why I don't like roadmaps:

@RickStrahl Maybe it's due to some code interpreting and translating a certain path incorrectly.

What are these people doing to try to open a folder in a \\.\nul path? How is that even possible from a UI operation (directory listing from a folder browser)

@jasonfried They have busy lawyers. Better be safe than getting sued.

Have you seen the fine print at the bottom of Apple's website lately? Must be a world record for the longest footer.

@mkristensen @VS_Debugger Nice. OzCode and CodeRush's debugger visualizer had it for years.

Visual Studio 2026 shows the results of if-statements inline during debugging. Coming soon...

@mehulharry @RickStrahl I am getting older and I would look into step thru ones. I am not following the market.

@abdu3000 @RickStrahl Thanks, yes, just started this year. eBike enthusiast?! Any recommendations for an eBike? :)

Having pretty good luck running the Visual Studio 2026 Preview for all VS tasks over the last week. Overall it feels a bit more snappy and the compressed top menu and bottom panels are saving some vertical space, but other than that this is more of an incremental improvement than some major rework. For all the hype of 'AI Integration' I have not run into anything that actually is affected by any AI improvements. They might be there with CoPilot specifc Chat operations (like @ Profiler Assistant) but as to AI integration I don't see anything.

@mehulharry @RickStrahl Hi Mehul. I didn't know you work at Jetbrains now. Congrats!

@RickStrahl Love this take, Rick. Especially the part about R# working smoothly in the VS2026 Preview. If you’re up for it, we’d love to invite you to a small #ReSharper Insiders Slack for early previews + quick polls. Low-traffic, opt-out anytime. Happy to DM details.

@jmanuelsoberano @codeopinion @jetbrains It has always been using credits. Some people say the credits are being consumed faster now.

@codeopinion Switching to credits was a terrible decision. I ran out way too fast, even with the IA Ultimate plan. 😤 Before, when they ran out, I could still use a local model… but now with Junie, not even that. Really disappointed. @jetbrains #junie

Junie in Ryder/WebStorm has been pretty good. Speed seems to be a bit slow but I've been fine with the results. Makes iteration slower but I'll deal with it.

@hhrvoje @RickStrahl @danroth27 Blazor needs to get better, for it to get more adapted. Not the other way round. Blazor might be the future and therefore needs more attention. Just like WinForms is a mature and done technology, MVC Razor is heading that way. WinForms is also widespread but gets little updates

@RickStrahl @danroth27 which is quite interesting because all projects I've been consulting or companies I worked for uses Razor (and MVC, rarely I see Razor Pages). Shouldn't the effort be driven by stats? Are people really using Blazor so much, and static pages + SPA?

Kinda pissed about this change. I use RazorRuntimeCompilation for a lot of things. LiveReloadServer uses it for loose Razor support. I imagine any of the Razor Templating solutions are going to break because of this too. Bad move! #aspnet github.com/aspnet/Announc…

@nickchapsas I meant 2025.2

@nickchapsas Sonnet 3.7 and 4 cost the same, therefore no point for them to switch. I don't see your issue on my side. Use Rider EAP and check for updates every day. WebStorm 2024.2 was released today.

I'm so tired of JetBrains' AI Assistant sneakingly changing me to a cheaper model automatically after I run a prompt or while I am typing, as if I wouldn't see it. If you can't afford to offer an AI Assistant, don't offer it.

@CatcherOfALie @MarkWarner Your experience doesn't mean it never happens. To no one!

You’ve planned and saved for months to take your family on that dream vacation. You buy amusement park tickets. Then, you go to buy the flights, except all of a sudden… the price has skyrocketed. Why? Because your airline knows you just purchased those tickets.

@RickStrahl @datagrip I hate how database objects such as tables can only be shown under their schema in Datagrip. There's no way to display them in a flat hierarchy like SSMS. Plus the fact that after installation, objects are hidden because namespaces option is unchecked by default.

Personally I mostly use JetBrains @datagrip for most of my 'standard' database access, since it supports all sorts of data backends, but for some things SSMS still is easier to work with - creating DBs dealing with permissions, and other administrative tasks that I need once in a blue moon and don't know off the top of my head to run SQL commands for. All that said the 'new' UI is sort of new, but there's a lot of stuff that brings up the old Windows. The Admin stuff in particular continues to be painful with blocking UI, and error messages that don't leave you any the wiser when something's blocked.

Very happy to see that the new versions of SQL Server Management Studio (v21+) can update with the VS Installer. Besides being easier to manage, then new version is also significantly faster for many things and has at least a few UI improvements. If you're still on the old version (which doesn't auto-uprade to to the new UI) definitely check out v21 that runs in the VS2022 shell.