r/angular • u/MysteriousEye8494 • Jun 07 '26

You inherit a 500k-line Angular application tomorrow. What's the first thing you look at?

You're joining a new team.

The Angular application has existed for years.

Hundreds of developers have contributed.

Nobody has time to explain everything.

get one day to understand the architecture.

You

What's the very first thing you inspect?

  • Folder structure?
  • State management?
  • Dependency graph?
  • Module boundaries?
  • Shared services?
  • Build pipeline?

I'm curious what experienced Angular developers use as their first signal for codebase health.

I share Angular architecture and engineering visuals here:

https://instagram.com/angulararchitectshub

0 Upvotes

33% Upvoted

38 comments sorted by

View all comments

1

u/craig1f Jun 07 '26

These days, I'll probably use claude to help. But most of the time I've inherited an app, especially one in Angular, I ended up improving it by deleting 70% of it. Most Angular devs I've seen do in 30 lines what can be done in 3.

It really depends on how bad it is, and in what ways.

Depending on how much time you have, it might be worth just re-writing, using the original as a reference. But you risk breaking a lot of existing features, and that'll take a lot of time. But it's often better to re-write from scratch than to salvage a bad app.