📰 Dev.to · ujja

I Love Dogs, But Dogs Scare Me — So I Built Pawsitive with Gemini 🐾.

Turning Ayurveda’s Six Rasas Into CSS Art

Rasa — Designing a Landing Page That Feels Like Opening a Food Journal

You Know What's Worse Than Not Being Able to Log In?

You Know What Happens When There's a Bug in Authentication? Absolutely Nothing.

Passion Atlas: A Living Map of Human Curiosity

From Govhack Win to Something That Actually Matters

I built my own event bus for a sustainability app — here's what I learned about agent automation using OpenClaw

Revisiting Idris in 2026: Is It Ready for Real Work?

What It Really Takes to Migrate 20+ Domains and 100+ SQL Tables from .NET to GraphQL

We’ve leaned on generative AI to make navigating our legacy Angular code less painful. The stats in this blog, like which components are purely legacy versus newly added are analyzed by Claude Code.

How We’re Surviving 600+ Legacy Angular Components While Migrating to Next.js, GraphQL, and a Monorepo

Shadow DOM Tailwind and shadcn/ui all have their strengths, but they do not always play nicely together. Sometimes you just have to compromise. Use Shadow DOM only for simple components, let portals work normally, and accept a bit of global CSS.

I Know This Will Upset Some Devs, but Tailwind + Shadcn/ui + Shadow DOM = Pain

Anyone who’s tried to stitch React into an Angular codebase knows it’s not magic. Web Components help—but they also introduce their own quirks (looking at you, styling + change detection 👀).

Web Components in Angular: Integrating React Components Across Framework Boundaries