A solution is objectively better only if it moves the codebase forward towards the business objectives. More often that not this involves no refactoring but surgically adding features without changing or breaking any existing functionality.
A solution is objectively better only if it moves the codebase forward towards the business objectives. More often that not this involves no refactoring but surgically adding features without changing or breaking any existing functionality.
At some point a Senior Engineer is about Engineering. Leave the marketing to that department.
The idea that 'business objectives' can be meaningful in detail at the Engineering level is hopeful. Maybe in a startup with one product, and even then, everybody is guessing about what features will resonate and what the customer base is.
No, a Senior Engineer is first about competent correct performant code. That's got to be their focus. Not attending business meetings.
The engineers you are describing are some of the biggest time wasters I have seen - spending months on making “engineering improvements”. One guy I met spent a year on making the perfect build system in rust lang that I could have written in cmake and bash in a week.
This has reduced to cherry-picking bad examples. I think we both understand the issues by now.