Sometimes it can be helpful to try and fast-forward through time. Imagine you are writing your own new code. You&#x27;ve got it working well. You&#x27;ve spent some time thinking about it, so you&#x27;ve left room for growth and made it extensible so that next time a new feature comes along you don&#x27;t have to rewrite the whole thing. Then a new dev onboards and starts redoing things you&#x27;ve already done.<p>Right now you&#x27;re the new dev. Yes, you are going to have a lot to learn about code that&#x27;s already in place. Totally greenfield development is fairly rare. You don&#x27;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.<p>&gt; That&#x27;s great for the business but not much fun for me.<p>That&#x27;s why we call it &quot;work&quot; and not &quot;play.&quot; :)