A fellow senior engineer on my team is leading a large multi year project that involves rewriting a significant portion of the codebase. He came up with the proposal, design doc, everything. A couple of team members are already helping him in the project, but since the project's scope is so big, he needs more help.
There is also a backlog of other projects that haven't been prioritized for several quarters. These include stuff like migrations, enabling CD (we still deploy manually taking up plenty of oncall engineer's time everyday) for our service, etc.
I feel like I would get more credit and build trust towards moving to E6 by leading one of the projects in the backlog as opposed to helping out the other engineer in his project. What do you recommend?
My immediate reaction is leaning "no" on this refactoring project and trying to come up with your own scope. Here's why I'm not too bullish on the rewrite effort:
That being said, there are some reasons why you would want to take this on. Here are some questions to ask
I also have some thoughts on picking up a new project from the backlog: