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
L'IA vocale en gestion de chantier : retour d'expérience après 50 projets BTP Le problème : les mains pleines, le temps compté Sur un chantier, le chef de projet ou l'artisan a les mains occupées. Qu'il soit en train de mesurer une façade, de vérifier l'aplomb d'une cloison ou de valider du béton fraîchement coulé, la dernière chose dont il a besoin est de sortir son téléphone pour re
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
Voice AI for Jobsite Estimating: A Developer Perspective Building estimators spend hours hunched over spreadsheets, struggling with poor handwriting on site photos, and entering the same data twice (once on paper, once in the office). This workflow is broken. Voice AI changes everything—and it's simpler to implement than most developers think. In this article, I'll walk you through the real-worl
Voice AI for Jobsite Estimating: A Developer Perspective The construction industry has historically lagged behind in digital adoption. Yet today, one of the most transformative shifts happening on job sites isn't coming from enterprise software vendors—it's coming from applied AI at the edge. Voice-based estimating is reshaping how builders create quotes, manage materials, and streamline workflo
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