Yes that would be a shame. I think usually those changes do get recognized but perhaps for the wrong reasons. While it's fine to recognize how much profit the b

Yes that would be a shame. I think usually those changes do get recognized but perhaps for the wrong reasons. While it's fine to recognize how much profit the business is making, the engineering role should be recognized for how well the system is implemented and working. It's a subtle but important difference. I have seen so many teams with talented engineers yet they produce brittle code that breaks all the time and is hard to develop, and I suspect it's because they're constantly thinking about how their changes will add business value instead of how well the system is being engineered (which should indirectly add that value anyway).