I think that's rather naive. A lot of work engineers do involves either keeping systems afloat or minor alterations that in cohort lead to a new feature but eac

I think that's rather naive. A lot of work engineers do involves either keeping systems afloat or minor alterations that in cohort lead to a new feature but each minor alterations itself not doing anything meaningful. Evaluating individual or even team impact in those cases is _hard_. Yes, product people or in some cases managers do it but most of their numbers come with five asterisks to cover their asses as they are largely bs. There are definitely people who are impactful enough and deserve to make bold "I" statements but they are in the vast minority.