3 ms·

I am a senior dev managing a large and relatively messy codebase. Let's see if the way I read the situation checks out: > I've already made some comments about

I am a senior dev managing a large and relatively messy codebase. Let's see if the way I read the situation checks out: > I've already made some comments about rewriting it and the response was basically "ok". This means that the person in charge of the code is probably aware of its shortcomings. > The person in charge of this project was working on it alone This suggests that probably the codebase started out in a neat form and became messy over time due to understaffing/bad planning/feature creep. There is only so much he/she could do as an overworked single dev having to manage a large system. Your senior is probably very happy to have another dev helping with this. I wish I had someone helping me. Take it as an opportunity, dealing with legacy is a challenge but you can grow a lot as a developer!

BaronVonSteuben 8y ago
> Take it as an opportunity, dealing with legacy is a challenge but you can grow a lot as a developer! I agree, but it's fraught with risk, and could also turn into an opportunity to spend several months or even years being miserable, and thought a mediocre to poor developer because you aren't able to deliver fast enough. This becomes especially true when the original developer is there and can probably do things 10x faster (which will make you look bad). You'll need to make sure you're having regular one on ones and keeping your team lead/manager up to date on the work you're doing. Perception is more important than anything. If you save the world but do it quietly, nobody will know, and they'll decide you aren't productive enough.
- mastazi 8y ago
  > If you save the world but do it quietly, nobody will know, and they'll decide you aren't productive enough. I agree, I think OP should find a way to present his work as a "project" that makes sense to management... A good example, someone else in this comments thread suggested that OP could create an API around the legacy core. Creating an API is something that can be "sold" well to management.

BaronVonSteuben 8y ago

> Take it as an opportunity, dealing with legacy is a challenge but you can grow a lot as a developer! I agree, but it's fraught with risk, and could also turn into an opportunity to spend several months or even years being miserable, and thought a mediocre to poor developer because you aren't able to deliver fast enough. This becomes especially true when the original developer is there and can probably do things 10x faster (which will make you look bad). You'll need to make sure you're having regular one on ones and keeping your team lead/manager up to date on the work you're doing. Perception is more important than anything. If you save the world but do it quietly, nobody will know, and they'll decide you aren't productive enough.

mastazi 8y ago
> If you save the world but do it quietly, nobody will know, and they'll decide you aren't productive enough. I agree, I think OP should find a way to present his work as a "project" that makes sense to management... A good example, someone else in this comments thread suggested that OP could create an API around the legacy core. Creating an API is something that can be "sold" well to management.