Asif Sadat
← All writing
LeadershipFeb 20261 min read

How I moved a team off Angular without a rewrite

The win was never "React is better." It was de-risking a framework change and bringing people with me.

Draft outline — replace with the real story.

Every "we should switch frameworks" conversation dies the same way: someone says "rewrite," everyone pictures a six-month freeze, and the idea is buried. Here's how we moved off Angular without ever stopping shipping.

Why the question even came up

What was actually hurting? Be specific — hiring, build times, the parts of Angular the team kept fighting. Avoid "React is trendy."

Selling the migration, not the rewrite

The pitch that worked: no big bang, no freeze. New surfaces in React, old ones left alone until they were worth touching. How did you get buy-in from people who'd built the Angular app?

Making it boring on purpose

The de-risking moves — the seam between the two stacks, what you migrated first, how you proved it before asking anyone to commit.

Bringing the team with you

The human half. Pairing, the first PRs, the skeptic who became the advocate. This is the part hiring managers actually read.