
Run Claude Code for FREE with Ollama
Run Claude Code against a local AI model on your own PC - free, private and offline. Install Ollama, pick a model for your hardware, fix the context length, and connect it with ollama launch claude.

Run Claude Code against a local AI model on your own PC - free, private and offline. Install Ollama, pick a model for your hardware, fix the context length, and connect it with ollama launch claude.

Every new screen adds another repository method with its own copy of the same Where, Include and OrderBy. The Specification pattern gets the interface down to two methods that never change again - with exactly the same SQL.

Why AI models hallucinate and the one idea that fixes it in almost every production AI system - Retrieval-Augmented Generation. Chunking, embeddings, vector search, prompt augmentation, and the four places RAG breaks.

Claude can write C# but has no idea what's in your database until you give it a way to ask. Build your first MCP server in .NET 10 with EF Core and SQL Server, expose three tools, and use it from Claude Desktop and MCP Inspector.

Two real production scenarios on a 1-million-row catalog - a tiered pricing promotion and a live CSV feed import - with numbers measured on camera: where a hand-rolled EF Core loop is fine, and where BulkUpdate, BulkMerge, and BulkSynchronize from Entity Framework Extensions turn 51 seconds into 12.

Your multi-tenant EF Core app might be leaking one customer's data into another customer's response right now - here's how EF Core 10's named global query filters fix that for good.

Build a self-contained EF Core migration bundle in GitHub Actions, apply it to Azure SQL as a dedicated deploy step, then ship the API to App Service - schema and code moving together, with a smoke test at the end.

Partial classes are not just a way to split a big file in two. Splitting generated code from hand-written code, partial methods as optional extension points, and why EF Core's scaffolding leans on this feature so heavily.

Calling Database.Migrate() on startup is the demo answer, not the production one. How to actually ship schema changes - idempotent SQL scripts, migration bundles, a least-privilege migration login, and reviewing what EF generated.