dariocp retweeted
Un amigo me dijo: «Hace 6 meses que uso IA y todavía no hice un agente».
Me hizo pensar: mucha gente usa ChatGPT todos los días, pero nunca construyó nada.
Vamos a empezar por algo simple: un agente del clima conectado a Open-Meteo. 🌦️
Te cuento cómo 👇
Building RAG or semantic search in .NET? 🧠🔎
Microsoft.Extensions.VectorData abstracts the vector store so your app can upsert embeddings, run similarity searches, filter with LINQ + switch database providers (cont) msft.it/l/6013a0kST
dariocp retweeted
💗 New MAX30100 support in .NET @nanoFramework!
Bring heart-rate and pulse-oximetry sensing to your C# embedded projects with integrated red/IR LEDs, photodetection and low-power operation. 🚀
#iot #embeddedsystems #sensors #dotnet
🟣 Say hello to dotnetup!
.NET’s new toolchain manager brings user-local installs, side-by-side SDKs/runtimes, channel tracking, global.json support + preview/daily builds. ⚙️🔥
Less toolchain wrangling. More building. 🚀
👉 Read: msft.it/6013avH3v
dariocp retweeted
Microsoft open-sourced an app that watches you do a task once, then teaches your AI agent to do it for you. 4.3K stars.
How Skill Recorder works:
1. Hit record (⌘⇧R or Ctrl+Shift+R) and do the task normally. You can talk through it out loud too.
2. It captures your clicks, app switches, pages and terminal commands, all on your machine.
3. GitHub Copilot turns the recording into a list of steps you can edit.
4. One click turns it into a skill your agent can run, or an automation on a schedule.
It generalizes from one example, so recording yourself submitting one form teaches the agent to submit all of them.
Runs on Mac, Windows 11 and Ubuntu. Needs a GitHub account with Copilot access.
Install: copy the one-line command from the latest release:
github.com/microsoft/skill-r…
10 MCP servers you need to install now as a .NET developer
blog.elmah.io/10-mcp-servers…
- they forgot to add T-SQL Analyzer ;-)
#dotnet #mcp #ai
dariocp retweeted
localhost:5001, localhost:5002, localhost:5217, localhost:6009...
"Wait, which port was the billing service again?"
If you've Dockerized more than one .NET API, you've been there.
One API feels fine. Then you add a second API. Then a UI. Then a webhook listener.
And suddenly your dev environment is:
A wall of random ports
CORS headaches
Auth redirect URLs that break behind a reverse proxy
A README nobody updates
The fix: Traefik.
It's a reverse proxy that auto-discovers your Docker containers and routes traffic based on labels. So instead of ports, you get clean local URLs:
http:// catalog.localhost
http:// billing.localhost
http:// traefik.localhost (optional dashboard)
Three labels on the service. That's it.
And the best part? Routing lives next to the service, not in a 400-line Nginx config nobody wants to touch.
I published a complete, real-world guide in my newsletter:
✅ Full .NET Minimal APIs
✅ Docker Compose setup
✅ Traefik explained step by step
✅ Why forwarded headers matter in ASP. NET Core
✅ Clean local domains that scale
🔗 Read it here: thecodeman.net/posts/dotnet-…
📌 Join 25,000+ engineers who read my newsletter every week: thecodeman.net 📌
dariocp retweeted
You should be using IHttpClientFactory to create your HttpClients in .NET.
But why is this the recommended approach?
3 options exist
Number 1: use the IHttpClientFactory directly. The downside is you'll have to configure the HttpClient every time.
If you want to get a pre-configured HttpClient, you can use named or typed clients.
Here's the right way to work with HttpClient in .NET: milanjovanovic.tech/blog/the…
I prefer working with a typed client in like 99% of cases. Refit also works.
🚨 Production app frozen?
Use C# to monitor ThreadPool health, detect saturation, and automatically capture memory dumps for post-mortem debugging. 💾🔎
Stop guessing. Start investigating.
📖 Read: msft.it/6187aWM29
dariocp retweeted
Meet Mistral Large 4, aka Le Chonk.
• 1T parameters, natively multimodal. 49B active.
It is the best open weights model from US or Europe on aggregated benchmarks.
• State-of-the-art on critical workloads, including cyber defense, manufacturing and finance and it surpasses closed frontier models on visual grounding.
• Forged in Europe end-to-end and is deployable from Europe via our own Mistral Cloud infrastructure.
• Available to all via API today. Working with cybersecurity partners privately.
Open weights release end of October.
🤖 Made with AI
🤖 AG-UI now has a first class .NET SDK!
Stream agent lifecycle events, tool calls, state updates & multi-agent workflows using a standard protocol. Less custom event parsing. More interoperable AI apps. ⚡
📖 Read: msft.it/6187altTH
dariocp retweeted
Group your code by feature, not by technical layer. It sounds like a small change. It changes how every change feels.
Here's the old way, the one most of us learned. Horizontal layers. Controllers in one folder, Services in another, Repositories in a third, DTOs in a fourth. Now add a single feature. You touch all four folders for one piece of work, and to understand that feature you go hunting across the whole solution.
Vertical slices flip the grouping.
One feature lives in one folder. A CreateOrder folder holds its endpoint, its command, its handler, and its validator, all sitting right next to each other. GetOrderById is its own folder with its own endpoint, query, and handler. Open the folder and the entire feature is in front of you. No jumping across five layers to follow one request.
The rule of thumb that keeps it clean: organize by feature first, technical layer second. Coupling inside a single feature is fine, that's just the feature holding together. Coupling across features is the thing you actually want to avoid.
You still keep a thin domain project for your entities and an infrastructure folder for shared persistence. But the day-to-day work happens inside one slice at a time.
Try this today: take your next new endpoint and build it as a slice. One folder, everything it needs living inside it. The first time you change that feature and never once leave the folder, you'll get why people don't go back.
Build your next endpoint as a slice before you judge it. If it clicks, repost it for a team still drowning in layers. I'm here posting .NET breakdowns most days, so follow if you want them in your feed.
Announcing Gemini 4 Argon, our new frontier model.
Argon is built to sustain deep reasoning across complex, long-horizon workflows and delivers frontier performance in complex workflows across real-world software engineering, enterprise knowledge work like legal and finance, and cybersecurity defense.
We’re also expanding the model’s output token limit to an industry-leading 1M tokens.
Argon is currently rolling out to a set of trusted cyber defenders in the Fairwind Program, with broader availability as soon as possible.
dariocp retweeted
Microsoft moved the GitHub Copilot runtime from TypeScript to Rust with AI agents. One engineer, ~3 weeks of dev time, $120K in credits, 800K lines.
Result: up to 21x faster in-process.
Nobody read every line. Here's how they reviewed it: youtu.be/dN11EApmfkM
dariocp retweeted
I made the only guide to JSONB in PostgreSQL you need.
You just need to dedicate 10 minutes of your time 👇
I can confidently say that PostgreSQL is my favorite database.
- It's free
- It's extensible
- It's frequently updated with new features
But my favorite feature is its comprehensive JSON support.
You can learn more here: pavle.codes/blog/jsonb-in-po…
Also, don't forget to subscribe to my newsletter at pavle.codes


























