|I'm currently working as a front end engineer (70% front end, 30% back end).|
When I used to briefly worked at greenfield projects where I get to play around with React, Redux, starting a component library etc, I was very excited and learned a'lot.
I was then moved to a team working on maintaining a legacy but critical codebase. Despite the fact that I tried to lie to myself by saying as a software engineer, I should be able to adapt to anything and place customer first. I was not happy and motivated.
For some reason, one year in, I'm not growing. To be honest, I am not interested in the old ways of doing things (e.g. Knockout, JSP) as I see no market value in them. I tried to reason with my manager the value of upgrading the tech, but the progress is very slow.
If my resume is only working on the greatest and latest, is that a bad thing? Does anyone else have a hard time trying to convince themselves the value of maintaining old codebases? How did you do it knowing when you apply at the next job interview, they will be asking up to date technical interview questions? I felt really dissapointed at myself at my inability to adapt...