We Rewrote Our Angular 18 App in React 20 and Increased Developer Velocity by 40% Last quarter, our engineering team made the bold call to rewrite our 3-year-old Angular 18 production application in React 20. After 6 months of development, we cut over to the new stack with zero downtime, and the results have exceeded our expectations: we’ve measured a 40% increase in developer velocity, alongsid
White labeling is more common than you might think. When developing software, you often need to deploy the same application for multiple clients, each requiring their own customization: unique color palettes, logos, or specific variants for a link. Without a proper strategy, you might be tempted to simply clone the existing repository and implement client-specific changes on demand. However, this
Confession: I’m not a walking dictionary. If you test me on textbook IT definitions, I might fail. After transitioning through Law and Banking into Tech, I’ve realized that terminology is often just a high-tech "smoke screen" for professional ego. But for many of us, the problem is deeper: it's about the language of logic itself. In my first year of Law school, I spent nights memorizing the "Theor
How I removed a legacy behavior that optimized for likability—and paid for it with self-respect. Context I recently ran an audit on a behavioral pattern I had been running for years: If (someone needs something) I thought this was a virtue. In practice, it behaved like an anti-pattern: It scaled poorly So I treated it like deprecated code and started a refactor. The Bug: Over-Availability as a Def
TL;DR: ng-prism lets you showcase Angular components by adding a single decorator to the component class itself. No story files, no parallel file tree, no framework mismatch. Just Angular. If you've ever maintained a Storybook setup for an Angular component library, you know the drill: for every component you write, you also write a .stories.ts file. Then you keep both in sync. Then so