When fixing legacy code, you can become a victim of your own success. The old crusty systems are usually the company money-makers. Once you show some success

When fixing legacy code, you can become a victim of your own success. The old crusty systems are usually the company money-makers. Once you show some success at fixing and maintaining them, you become the "go to" person for fixing them. That can be a good thing. It's a tough rut to get out of but I think you have some leverage if you choose to use it. New frameworks and new projects come and go, but that boring hideous legacy system is the one that survives and the one that brings in money to company. Use that to your advantage to get a raise, create some opportunity, or failing that, bounce to a different company. Greenfield is always more stressful to me. The deadlines are ridiculous and the requirements sketchy.