State Management: NgRx vs Signals
Comparing NgRx and Angular Signals by the complexity they introduce, the constraints they handle well, and the tradeoffs they impose on an Angular codebase.
Developer blog
Ben Halverson writes about front-end architecture, edge delivery, and keeping systems useful without making them harder to run than they need to be.
Comparing NgRx and Angular Signals by the complexity they introduce, the constraints they handle well, and the tradeoffs they impose on an Angular codebase.
I'm Ben Halverson, a web developer focused on Angular, TypeScript, and cloud-native delivery. I care about code that stays understandable under pressure, user interfaces that respect the reader, and deployment workflows that don't create hidden maintenance costs.
Most posts here focus on front-end architecture, developer tooling, performance, edge delivery, and the tradeoffs behind technical decisions. The goal is to publish things that are directly useful to other engineers, not generic summaries.
API and web application for intake, quoting, queue management, and fulfillment across custom print requests.
Computer vision experiments for RC vehicles, onboard perception, and human-in-the-loop control workflows.
A working collection of modeling experiments, printable parts, and workflow improvements for repeatable design work.
Comparing NgRx and Angular Signals by the complexity they introduce, the constraints they handle well, and the tradeoffs they impose on an Angular codebase.