> 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

> 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.