I recently refactored some code for a Bitovi client, Strategic Wealth Preservation. We used GitHub Copilot Agent mode with Claude Sonnet 4 to adjust the code formatting and linting rules for SWP's codebase.

Six months ago, one of our Angular Consulting clients needed help with their web app. The frontend was too complicated to test, and they weren’t sure how to fix it. Bitovi presented three approaches to help simplify the frontend code and make testing it easier.

Node.js is one of the most popular languages for web servers, even though JavaScript is single-threaded. This might seem contradictory at first—don’t web servers need to handle simultaneous connections?

Enabling strict modefor TypeScript is one of the best ways to ensure code quality on a project. It forces developers to handle edge cases and avoid risky type coercions. It also exposes hidden bugs.

Slow builds stop developers' productivity cold. If code takes even two minutes to compile, it’s easy to get distracted. You lose your train of thought or, god forbid, open social media.

RxJS 7 has shipped! For us Angular developers, it unfortunately did not ship in time for Angular 12.

This post is a continuation from Part 1, where we set up a test project with NgRx and ngrx-forms in our Angular application. For part 2, we will validate our form.

If your Angular application already uses NgRx, you know the value of writing good reducers and using one-way data flow. However, that knowledge may not be enough to keep the biggest form in your app from being a rat’s nest of FormGroups and related logic. Forget keeping components under 50 lines of code - your form logic alone blows past that.