Sometimes it can be helpful to try and fast-forward through time. Imagine you are writing your own new code. You've got it working well. You've spent some time

Sometimes it can be helpful to try and fast-forward through time. Imagine you are writing your own new code. You've got it working well. You've spent some time thinking about it, so you've left room for growth and made it extensible so that next time a new feature comes along you don't have to rewrite the whole thing. Then a new dev onboards and starts redoing things you've already done. Right now you're the new dev. Yes, you are going to have a lot to learn about code that's already in place. Totally greenfield development is fairly rare. You don't have to learn the whole codebase (almost no-one does in large projects), but it would be wise to solicit input about where you should start looking before writing brand new code for a new feature. > That's great for the business but not much fun for me. That's why we call it "work" and not "play." :)