Most of what people hate about data centers is factually incorrect or aimed at the wrong target.
The remaining concerns trace back to policy failures: unnecessary subsidies, sluggish permitting, antiquated power rules. Fix those, and the problems dissipate, says @scottlincicome.
https://t.co/l0XIC4W7b2
@kamilogorek Coding agents have definitely added more context switching to my day. But that's the reality of a "manager schedule". I'm delegating to agents to do the deep work. With agents everyone is now a manager.
Introducing Gemini 3 Flash, our frontier intelligence model, available at scale for everyone. It excels at coding, tool calling, and is stronger than 2.5 Pro across most metrics!! ⚡️
Available in the API at $0.50 in / 1M tokens and $3.00 out / 1M tokens across.
GPT-5.1, GPT-5.1-Codex, and GPT-5.1-Codex-Mini, the full suite of OpenAI’s latest 5.1-series models, are now rolling out in public preview in GitHub Copilot.
Try it out in @code.
https://t.co/H5XFsmaXyC
Introducing Claude Sonnet 4.5—the best coding model in the world.
It's the strongest model for building complex agents. It's the best model at using computers. And it shows substantial gains on tests of reasoning and math.
New in Visual Studio: GitHub Copilot Diagnostics for .NET 🧑💻
✅ Smarter breakpoints
✅ LINQ query help
✅ Exception summaries
✅ Deadlock insights
A smoother debugging experience, right in your IDE.
#GitHubCopilot (cont) https://t.co/WftgMsXBzK
Becoming a better writer also makes you better with AI.
I'm seeing this with devs using agents. Some are having a great time, others not so much. The difference is usually how well they write (e.g. give context).
Try documenting how you build software in AGENTS.md. It's hard!
Every token matters, so being concise is important. But you also have to find the right balance of determinism vs. style and preference.
You can still use type checking, linters, formatters, and other tools. Your job is steering the agent in the right direction and making clear which tools it has available (e.g. commands to run tests or linting).
But you likely have additional context about how you (or your team) prefer to build software that isn’t captured by those tools. For example, more on the system design and architecture.
A classic React example is: do you prefer a single component per file, or multiple components in the same file?
What level of abstraction do you want? You might tell the agent to only move things to a `lib/` folder if they have been used 3 times, otherwise just copy/paste.
Anyone doing this well? I'm on the hunt for AGENTS/CLAUDE/Cursor rules for inspiration. They should be concise, personalized, and very intentionally written.
GM!
Grok-4 coding is rumored to be pretty good!
Deepseek v3.1 is just a marginal improvement
Nano-banana is showing an astonishing capability to follow instructions well
The @code team is hard at work improving the agent prompts - always.
If you've got Insiders you can try the new agent system prompt for GPT-5 today.
Let us know how it works!
We’re introducing an all-new voice assistant that will provide the next-gen of help at home 🥁 🥁 🥁 Gemini for Home—enabling hands-free help for the entire household.
And that’s not all, @GeminiApp is also coming to your TV this fall!¹ https://t.co/xrr0KhzmK6 #MadeByGoogle
Opus+Sonnet to build features, GPT-5 to verify and debug them (via codex-cli) is my corrent dream team.
Codex/GPT isn't an agent of many words but seems to dig deeper and finds the actual issue vs Claude's fake "I see the issue now" and randomly changing shit,.