> "impact" is almost always measured by what features you shipped rather than considering the impact your code had on the long-term maintainability of the codebase

A new feature = an increment in major version of your product, for example v1.0 -> v2.0

Bug fixing and other maintenance work = an increment in minor version, for example v1.0 - v1.1

No matter how many bug fixes or perf improvement you did, v1.999999 is always less than v2.0. It's a pretty sad fact.