I just read the Jan/Feb 2026 issue of CODE Magazine. A few trends stood out that seem to contradict the usual enterprise inertia:
1. Agentic AI / SmolAgents The focus is shifting from LLMs as chatbots to "agents" that execute tasks. The issue covers SmolAgents (Hugging Face), distinguishing between "Code Agents" (which write/execute code logic) and "Tool Calling Agents". It frames this as the move toward AI that can reliably handle API interactions without hallucinating as much.
2. Polyglot .NET (Rust integration) There is a significant piece on building distributed apps using Rust for performance-critical services, orchestrated by .NET Aspire. It’s interesting to see a Microsoft-centric publication pushing Rust/C# interoperability (via Protobuf) rather than just "optimize your C# code."
3. The End of CLI? (Model Context Protocol) The Angular article argues that the CLI (ng generate) is becoming legacy. The proposed replacement is MCP (Model Context Protocol), allowing local LLMs to understand project context and handle scaffolding via natural language.
4. Postgres as the default The issue treats PostgreSQL as the de-facto standard for modern .NET development, further signaling the decline of MS SQL Server dominance in greenfield projects.
Has anyone here experimented with MCP in production yet? The "death of CLI" claim feels bold, but I'm curious if the DX actually justifies it.
1. Agentic AI / SmolAgents The focus is shifting from LLMs as chatbots to "agents" that execute tasks. The issue covers SmolAgents (Hugging Face), distinguishing between "Code Agents" (which write/execute code logic) and "Tool Calling Agents". It frames this as the move toward AI that can reliably handle API interactions without hallucinating as much.
2. Polyglot .NET (Rust integration) There is a significant piece on building distributed apps using Rust for performance-critical services, orchestrated by .NET Aspire. It’s interesting to see a Microsoft-centric publication pushing Rust/C# interoperability (via Protobuf) rather than just "optimize your C# code."
3. The End of CLI? (Model Context Protocol) The Angular article argues that the CLI (ng generate) is becoming legacy. The proposed replacement is MCP (Model Context Protocol), allowing local LLMs to understand project context and handle scaffolding via natural language.
4. Postgres as the default The issue treats PostgreSQL as the de-facto standard for modern .NET development, further signaling the decline of MS SQL Server dominance in greenfield projects.
Has anyone here experimented with MCP in production yet? The "death of CLI" claim feels bold, but I'm curious if the DX actually justifies it.