The less is better.

If you're not decreasing the codebase, then you have to increase your time spent on the codebase.
Of course, it's a liability. You gotta read it 10, 100, gazillion times to maintain it in the future.

More code, more tests.
More code, more stress.
More code, more build time on CI.
More code, more jira.
More code, more "who the fuck wrote that shit?"
More code, more "Oh, that was me wrote that shit."
More code, more spendings on AWS.
More code, more developers to maintain it.
More code, more bureaucracy.
More code, more boss wants to fire you.

More code, the less productivity.
More code, the less time with family.
More code, the less healthy life style.
More code, the less time on gym.
More code, the less time on your side-hustle.

The best code not written code at all.

- Do you need it in the first place?
- Are you doing the refactor for the sake of refactoring?
- Are you doing the refactor hyped about the new framework?
- Do you need that abstraction at all?
- Could you fix it by not adding 1 line of code but by removing 2 lines?

There are million ways you can waste time in real life.

Filling garbage in the garbage codebase to maintain that garbage in order to be proud of garbage amount is not one of them.

Think 10, 20 times, before you push it. Do you need it?

@Diyorbekk_dev