Angular · JavaScript
Angular signals and change detection, plus the JavaScript scoping, prototype, and higher-order function patterns that decide whether a frontend codebase stays maintainable.
Featured Articles
Practical lessons from building Angular applications in production: when signals actually reduce change detection work, and why readonly doesn't prevent signal updates.
Middleware chains, composition pipelines, memoization, and configurable validators, the higher-order function patterns behind real enterprise JavaScript codebases.
Five real JavaScript scoping bugs: the var-in-a-loop async trap, implicit globals, variable shadowing, the temporal dead zone, and block-scope leaks.
Lost this context in callbacks, shared mutable state via the prototype, forgetting new, and prototype pollution, four real bugs with fixes.
Frontend performance and maintainability depend on how application state changes, how components are composed, and how browser behavior is understood. In Angular, signals can make dependencies explicit and reduce unnecessary change-detection work when used with a clear state model. In JavaScript, closures, scope, prototypes, and the value of this explain many bugs that otherwise appear only in larger applications or asynchronous flows.
The articles in this collection use concrete examples to explain when these patterns help, where they can fail, and how to reason about their tradeoffs. Use them as focused references when reviewing a codebase, debugging a production issue, or choosing an implementation pattern. Continue with the Angular engineering notes and the related JavaScript guides on functions, scoping, and prototypes.