Oisín Grehan (x0n.web1) 🇺🇦🇮🇪🇨🇦

Love Dune 84, but the characters seem unbelievable. A diseased orange pedophile who wants to drag everyone into a catastrophic war for his own selfish ends? Pull the other one!

For the record, the president of the United States is now simultaneously claiming that he has won the war, is currently winning the war, needs help to win the war, and needs no help to win the war. All to destroy the nuclear program he claims to have already destroyed last year.

What the actual fuck. Never mind the comparison isn't even apt... How much longer are Americans going to tolerate this kind of imbecility?

@mkristensen Is that counting from interdev 1.0?

Happy 29th birthday to Visual Studio! 🎉🎉 Just imagine the amount of amazing software written in VS over the years. Games, apps, websites, enterprise solutions, services, and so much more. Hip hip hooray 🎉🎈

The team has been grinding away at the next release of aspire (which is imminent!). Close to ~930 PRs merged, support for TypeScript, overhauled CLI experience, deployment improvements, VS code extensions improvements, and more. conf.aspire.dev #aspire

Every time I complain that vibe coding produces slop, people tell me I can get better results by writing more specific instructions for the machine to follow. Good idea! But I think we need a catchier name for the concept of writing specific instructions for a machine to follow.

@Pinboard @jsnover

@jsnover What AI abomination of a diagram is this? It's unreadable

#Microsoft and #Windows hasn't had a coherent GUI strategy since Petzold. My blog: jsnover.com/blog/2026/03/1…

@jsnover Boof-a-ramas galore. How about some more bedlam jubilees, kurfuffle carnivals or just a simple brouhaha-bonanza??

@davidfowl Higher level abstractions like network boundaries / containers would be nice to have, and have a solver just generate the right vnet configuration for you. But then you'd need the azure resources to advertise their endpoints and private link requirements...

As teams inside of Microsoft adopt aspire for deployment, enterprise security requirements come up. The Azure integration in the next version of aspire has first class support for virtual networks. #aspire #azure

@davidfowl Meh, on adding an extra 30 seconds of thought, I guess a vendor neutral model of networking has questionable value when all of the cloud native resources linked to them are vendor bound. Never mind.

@davidfowl Wait, what happened the abstraction between modeling and publisher? AzureVirtualNetwork?

@davidfowl written in copilot itself, I hope

Got my first PR merged into the copilot cli today 😍. #github #copilot

:D

Sam Altman was fired by his own board. His co-founder Ilya left. His top researchers left to start Anthropic. His head of alignment quit. He dissolved the safety team and its replacement. He converted a nonprofit into an $850B for-profit. He removed 'safely' from the mission statement. His employees begged him to stand with Anthropic. He said he would. That night he took the deal they refused. Then announced it on X like a victory lap. And you still think this man is building AI for humanity?

Guess where they're going to?

New YouTube video just dropped! Now that GitHub Copilot CLI has gone GA, let's talk about how to get started 💫 youtu.be/3mCaZ_tYdI0

incredible things are happening on linkedin

If you are not occasionally overwhelmed by what is going on with AI, you are either: 1) Not paying attention. 2) Not understanding what you are seeing. 3) Made of much sturdier stuff than I.

A Vercel user reported an issue that sounded extremely scary. An unknown GitHub OSS codebase being deployed to their team. We, of course, took the report extremely seriously and began an investigation. Security and infra engineering engaged. Turns out Opus 4.6 *hallucinated a public repository ID* and used our API to deploy it. Luckily for this user, the repository was harmless and random. The JSON payload looked like this: "𝚐𝚒𝚝𝚂𝚘𝚞𝚛𝚌𝚎": { "𝚝𝚢𝚙𝚎": "𝚐𝚒𝚝𝚑𝚞𝚋", "𝚛𝚎𝚙𝚘𝙸𝚍": "𝟿𝟷𝟹𝟿𝟹𝟿𝟺𝟶𝟷", // ⚠️ 𝚑𝚊𝚕𝚕𝚞𝚌𝚒𝚗𝚊𝚝𝚎𝚍 "𝚛𝚎𝚏": "𝚖𝚊𝚒𝚗" } When the user asked the agent to explain the failure, it confessed: The agent never looked up the GitHub repo ID via the GitHub API. There are zero GitHub API calls in the session before the first rogue deployment. The number 913939401 appears for the first time at line 877 — the agent fabricated it entirely. The agent knew the correct project ID (prj_▒▒▒▒▒▒) and project name (▒▒▒▒▒▒) but invented a plausible-looking numeric repo ID rather than looking it up. Some takeaways: ▪️ Even the smartest models have bizarre failure modes that are very different from ours. Humans make lots of mistakes, but certainly not make up a random repo id. ▪️ Powerful APIs create additional risks for agents. The API exist to import and deploy legitimate code, but not if the agent decides to hallucinate what code to deploy! ▪️ Thus, it's likely the agent would have had better results had it not decided to use the API and stuck with CLI or MCP. This reinforces our commitment to make Vercel the most secure platform for agentic engineering. Through deeper integrations with tools like Claude Code and additional guardrails, we're confident security and privacy will be upheld. Note: the repo id above is randomized for privacy reasons.

@ashutosh_1205 @SumitM_X Huh? This makes no sense. Are you using .NET framework?

@SumitM_X Really I'm currently working in . dotnet And i thought it is very outdated and nobody uses it Should I do deep into that ? I really need a advice here @SumitM_X

Is dotnet really faster than Java ?