jmojeda

The Day I Integrated GitHub Copilot SDK Inside My XAF App (Part 2) jocheojeda.com/2026/02/16/the… integrate the GitHub Copilot SDK directly into a DevExpress XAF application, transforming a traditional business app into an AI-powered assistant. @jjcolumbie @DevExpress_XAF

🧠 3 ways to build RAG in .NET — using local embeddings! 🔍 Retrieval-only with VectorData 🦙 Turnkey RAG with Kernel Memory + Ollama 🏗️ Full manual pipeline with Foundry Local 👇 Code samples + walkthrough: elbruno.com/2026/02/14/%f0…

The Day I Integrated GitHub Copilot SDK Inside My XAF App (Part 1) jocheojeda.com/2026/02/16/the… This week, while studying Russian every day, I noticed I kept relying on GitHub Copilot inside VS Code more than anything else. @jjcolumbie @DevExpress_XAF

Stop EF Core From Dropping Columns Automatically (Custom IMigrationsModelDiffer) youtu.be/VMjw1v2TX6Q?si…

Closing the Loop with AI (part 3): Moving the Human to the End of the Pipeline jocheojeda.com/2026/02/11/clo… Let agents write, run, test, read logs, inspect state, and iterate without you acting as QA. With Serilog, SQLite, and Playwright, the loop becomes observable and repeatable

NEW RELEASE ALERT!! We are staying on the forefront of AI innovation while strengthening the core cross-platform .NET open-source ecosystem. There is something for everyone in our Feb release👇.

Closing the Loop (Part 2): So Far, So Good — and Yes, It’s Token Hungry jocheojeda.com/2026/02/09/clo…

jocheojeda.com/2026/02/09/clo… By giving agents the ability to test, fail, and self-correct, we can move from endless prompting to true autonomous engineering — where humans define outcomes, not implementations.

Github Copilot for the Rest of Us GitHub Copilot isn’t just a code writer—it’s a context-aware work partner inside VS Code. jocheojeda.com/2026/02/04/git…

The Mirage of a Memory Leak (or: why “it must be the framework” is usually wrong) jocheojeda.com/2026/01/30/the… Memory leaks in managed runtimes are often mirages. What looks like a broken framework is usually memory retention caused by our own code.

What can .NET devs expect in 2026 for Wasm? 👇

Our annual State of WebAssembly is back (2025–2026) It recaps the biggest Wasm progress from 2025 and what’s (predicted) to land in 2026.

As an XAF Developer, What Should I Actually Test? jocheojeda.com/2026/01/21/as-… @jjcolumbie @DevExpress_XAF

Application Installers and Assembly Resolution Using the Legacy .NET Framework jocheojeda.com/2026/01/15/app…

Greenfield vs Brownfield: How AI Changed the Way I Build and Rescue Software jocheojeda.com/2026/01/12/gre…

The DLL Registration Trap in Legacy .NET Framework Applications jocheojeda.com/2026/01/08/the…

ConfigureAwait(false): Why It Exists, What It Solves, and When Context Is the Real Bug jocheojeda.com/2026/01/08/con…

Structured RAG for Unknown and Mixed Languages jocheojeda.com/2026/01/05/str…

jocheojeda.com/2026/01/05/rag… RAG with PostgreSQL and C# (pros and cons)

ODBC: A Standard That Was Never Truly Neutral jocheojeda.com/2025/12/23/odb…