# How do you justify keeping a legacy product alive? — retained record

> Retained reddit record from reddit:ExperiencedDevs.

Canonical: https://highsignal.app/data/records/8c5ec9c25b9af415

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:ExperiencedDevs)  published 2026-09-21 02:44 ingested 2026-09-22 02:37

[original source ↗](https://www.reddit.com/r/ExperiencedDevs/comments/1wm0lc8/how_do_you_justify_keeping_a_legacy_product_alive/)

## retained text



```
Hi

I am currently the single developer managing a legacy product all by my own from design, development, implementation, testing to some extent and operations.

So far I have done a good job of it based on our last few releases this year where we had 0 incidents while the product had always caused at least 2-3 incidents per year in its last 5 years of existence.

Leadership and partner teams commended me on achieving this feat, which is good but my main concern comes from the fact that it is legacy where there is hardly any new features being offered.

Majority of the team is working on pushing out features to a modern version of this product with support from management to make the modern version flagship instead of the legacy one. But the legacy product has a pricing model which benefits most customers and it is the one pulling in the most revenue.

Moreover the legacy product has an operational overhead which eats up my additional time for being on call during releases without overtime payment.

The reason I am bringing so much context is to highlight my personal pain points that seems to make and break my career as well.

There are talks to move the legacy product into the modern version that keeps getting delayed because of other priorities. This would mean that operations become much smoother for the legacy product which would eliminate the requirement for me to do unpaid overtime for on call support.

While I take this as my personal win to avoid doing unpaid work, it could come as a loss for me as well because it would make me redundant to some extent, which puts me in direct path when the company starts doing involuntary reduction program in a few months or the next year. Voluntary redundancy already started.

Given the current market situation, I would prefer keep doing the unpaid work in order to avoid being made redundant at this point until something comes along while I keep trying for other opportunities.

I have made significant impact on the legacy product with actual metrics that I have personally tracked down over 12 months to justify my impact on the product. The architect rhetorically hinted that my product impact conflicts with their vision of migrating the legacy product to his shiny modern version since I seem to eliminate the pain points that he is fighting against without his new architecture taking the spotlight.

What strategy or advice would you provide to help me navigate this situation? My main concern is to not being made redundant to be in the radar of the V level executives while showing impact that such an expensive migration is not required as the architect envisions or delay it as much as I could until I can build my exit strategy.
```



document fetched 2026-09-22 00:25 · canonical https://reddit.com/r/ExperiencedDevs/comments/1wm0lc8/how_do_you_justify_keeping_a_legacy_product_alive
