Earlier quoted context omitted.
That is completely a mind game. Salient according to what criteria? Is he going to be happy to see wonderful high level distributed designs? Great coding practices at the micro level? Unit tests? Performance-oriented code? Ops greatness? CRUD boilerplate that any junior IC could jump into without much understanding (seems like this might be a stealth winner if he’s gearing up to build a skeleton crew of low-seniority…
> That is completely a mind game. Salient according to what criteria? Is what you do worth your salary? That is a pretty simple criteria, if you deliver significant value in basically any way that should be enough. Why do you think this is would be so hard? We had to write down reasoning like this to motivate our job at Google 1-2 times a year, it isn't hard to do.
My complaint isn't in the general concept of justifying your value. My complaint is in the request to have every coder in the company boil this down to such a simplistic representation of it on short notice in an environment where every indication is that it's going to be considered for a laughably small amount of time and then you might be fired on the spot if you didn't focus on the right axes.