Of course it's the role? Your generated value is always your individual contribution multiplied by the task that you chose to apply that effort to. If you rep

Of course it's the role? Your generated value is always your individual contribution multiplied by the task that you chose to apply that effort to. If you replaced an excellent CEO with a mediocre CEO or with a bad CEO, then you might see, from some baseline, doubling of the company's a value, or erasing it to nothing, based on which direction you decide to set the company and its culture. If you're the CTO for the company, your choice of team structure and how you choose to influence technical architecture could lead to productive happy teams or slow miserable ones. If you're the engineer in charge of writing a service, you could set your team up for tons of technical debt down the road, or a smooth running service that's easily and safely extensible. If you're doing a bugfix, you could spend the time to truly understand and solve the issue, or throw another if loop to the pile that the next person will find and have to understand before they can make their own patch to the code. So, if you have the ability to spend a day on a single effort, one which will improve the life of one developer, or one that would improve the life of all developers, or one that would improve the life of all employees, there's obviously a preference from the company's perspective. And then you can consider things like, improving the life of people who don't even work at your company, but that's generally done on your own time, unless the company thinks that the reputation that they gain is worth giving you the time.