One of the important lessons you need to learn is that code is a liability not an asset! All else being equal, from a balance sheet perspective having more code puts the company in a worse situation.<p>Your job as a software developer is, roughly, to deliver maximum business value with minimum cost, and that includes writing minimum code to accomplish the task. That is what the senior developers are talking about when they&#x27;re saying you&#x27;ve written too much code.<p>It does sound to me like they&#x27;ve got a well designed system if you can add new features simply by making a small modification and some configuration to the existing code. As long as it&#x27;s also well tested and well documented (that may be lacking...), you&#x27;ve got the ideal codebase: one in which you can add large amounts of business value with only incremental changes.<p>You mention that this is &quot;great for the business but not much fun for me&quot;. I think this is a sign of inexperience. Part of what makes something fun is how difficult it is. If something is too easy it&#x27;s boring; if something is too hard it&#x27;s frustrating. In the middle we find things fun. The reason writing lots of greenfield code is fun for you is because it&#x27;s easy. Understanding and modifying existing code is harder, and that&#x27;s currently too hard so you find it frustrating. You need to push past this stage to improve as a developer. As you get better, it will become easier to work in existing code and will stop being so frustrating.