AI can help you do your job, don't let it do your job. If AI does your job, well your not need then. There is no reason to compromise because we have AI.
This was an interesting trap that I already tried. One theory I had was that possibly we could lower the quality and compensate with AI. You might immediately think that's dumb but it's not as stupid as you think.
One of the interesting side effects of microservices was that it actually enabled less good software design. And it was a good thing. Because creating large monolithic applications requires a lot of diligence in design. But when you created microservices, because the scope was much smaller and there were fewer people working on it, you could get away with simpler, less rigid patterns. This actually increased agility with negligible effect on quality. And it wasn't bad. The bad thing about microservices is we just ended up with too many things and too many things cause a huge amount of maintenance overhead and a lot of decreased efficiency.
But what I'm finding with AI is if you reduce your expectation of quality and then you combine that with the implicit pressure to move faster, you get a compounding effect of really poor results over time. So with AI you very actively need to push back to slow down and keep quality but figure out how to enforce that quality more efficiently by leveraging AI.
Everyone who's getting so excited about the amount of crap they're pushing out with AI is just shooting themselves in the foot. Because that crap doesn't provide value. It basically just makes them look good on X for one day. Use AI to increase the value. Use AI to amplify the value that you have to offer.
Ever open a README just to remember how to reset the DB, run migrations, or mint a dev auth token?
In aspire 13.3, you can codify those onboarding tasks as resource commands. Humans can run them from the dashboard; agents and scripts can run them from the CLI.
#aspiredev
We've been working on this for a while -- it's impressive (and scary) to see the kinds of security issues it has identified.
Rolling out slowly, starting as a research preview for Team and Enterprise customers.
@trq212 To add to this...if you're getting either the "Another Claude process is currently running" or "Could not install - another process is currently installing Claude" message, execute "rm -rf ~/.local/state/claude/locks". This worked for me and 2.1.1 is working.
#Microsoft#AgentFramework now in public preview! Open-source SDK and runtime that simplifies orchestration for multi-agent systems—right from #AzureAIFoundry. 🚀🤖🤖🤖
Enterprise-ready and designed for your flow. Dive in and help shape the future: https://t.co/zEmJ0PUfo6
We have updated ChatGPT's personalization page: personality configuration, custom instructions, and memories are now all in one place. Going live over the next couple of days.
The Aspire team is cooking up a new (All) option for the console logs page.
Want everything at once? (All) gives you all resource logs in one view 🚀
#dotnet#aspire
This week the 1P squad were able to take some newly built aspire based services through and end-to-end multi region deployment 👏🏾. Still early days but we’re getting closer to a full stack story.
GitHub Copilot coding agent just got a major upgrade. ✨
What's new:
• It tests its own UI changes with Playwright and adds screenshots to PRs.
• It can connect to more context and tools with remote MCP support.
• You can trigger and track tasks from a new dashboard.
• It only uses one Copilot premium request per session.
Plus, it's now available for Copilot Pro and Business users. ✅
Here are all the updates in action. ▶️
The Remote GitHub MCP Server is here. 🔑🤖No more local installation needed, no more manual updates, no more runtime. Just copy the server URL, paste it into your MCP client, authenticate, and you're ready to go.
Try it yourself: https://t.co/1jczUOFMPT
@davidfowl Loved this & the bantz (in my experience, the better the bantz, the better the engineering 😆). More of this, please! Only good will come from sessions like this. 👏
Proud to raise the security standard... What if your container images came secure by default? Now they do.
NGINX is on board with Docker Hardened Images—SBOMs, SLSA, and sigs baked right in: https://t.co/xlWJiSwfKe
#Docker#NGINX#DevSecOps#SBOM#SLSA#ContainerSecurity