May 10 · 5 min read · AI agents are everywhere right now. But most learning resources still stop at: prompt engineering simple chatbot demos one-off RAG examples tool-calling snippets I wanted something more practica
Join discussionMay 2 · 14 min read · 🤔 Why Angular + .NET Core? Angular and ASP.NET Core together give you a rock-solid full-stack foundation for 2026 and beyond. Both are strongly typed, both are built with scalability in mind, and the
Join discussion
May 1 · 14 min read · 🤔 Why bother migrating? NgModules were Angular's original way of organising code. Every component, directive, and pipe had to be declared in exactly one module — and sharing anything between features
Join discussion
Apr 30 · 13 min read · 🤔 Why is this even a question? A few years ago the answer was simple: "use NgRx for serious apps." Today it's more nuanced. Angular Signals changed the game. You can now build reactive, scalable stat
Join discussion
Apr 29 · 15 min read · 🤔 The performance problem SSR was supposed to solve When you ship a standard Angular app, the browser receives a mostly empty HTML shell — just a <app-root></app-root> tag and a big JavaScript bundle
Join discussion
Apr 28 · 13 min read · 🤔 A little history first Angular has had three forms approaches over the years: Template-driven Forms (simple but hard to test), Reactive Forms (powerful but verbose), and now — Signal Forms (experim
VVartika commented
Apr 27 · 11 min read · 🤔 What even is Zone.js — and why did we need it? If you've been building Angular apps since the early days, you've probably never had to think about Zone.js. It just worked. But understanding what it
Join discussion
Apr 26 · 9 min read · 🎯 Why these two APIs matter right now Angular's Signals story has been building for three years. With Angular 20, the final pieces clicked into place: linkedSignal() and resource() both graduated to
Join discussion
