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
Applicant Tracking Systems used to be boring. For most of the 2010s, an ATS was essentially a database with a careers page bolted on top: a place to dump resumes, push them through a pipeline of stages, and email rejections in bulk. The interesting work happened around it, not inside it. That has shifted in the last two years, and the shift is deeper than the marketing pages suggest. I have spent
I used to send out application after application and hear nothing back. Not a single reply. At first, I thought my resume wasn't impressive enough. So I made it fancier. Added columns. Played with layouts. Tossed in some icons. Still nothing. Then I learned about Applicant Tracking Systems. Companies use software like Lever, Greenhouse, and Workday to scan resumes before a human ever sees them. If
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