It doesn’t matter if it’s about defending or explaining. Either one is an absolutely absurd situation to find yourself in where you have to explain stuff to people with zero context to save your job.
If I was given these instructions I’m out.
(I don’t have a horse in this race. I don’t work there. So not sure why you think I’m taking this personally)
That's your threshold for asking employees to summarize what they've been doing recently?
Management must have some profound interest in the feature being delivered and how it was implemented?
Question: have you ever managed people? And if so, how many?
I won’t go into your ad hominem.
While you're entitled to your opinion, it doesn't seem particularly relevant in discussions about whether or not this process is effective.
no one wants your code just for fun of it or it beying extra nice and smart. code is neded becauae it creates value.
The question itself comes from a place of authority, and the employee has nothing to gain, only to lose. Best case - I keep my job. Worst case - I get fired. That introduces stress into my life unnecessarily.
The new owners can go and read past evaluations instead of boiling the ocean. But, of course they won't do that. It's much easier to assert your authority and stress everyone out, to make sure they know that they are just resources churning out code.
If you step out of the soulless business mindset for one second, I'm sure you'll understand why asking me to prove my worth out of the blue is insulting.
"Prove your worth to the new gods, employee #1337!"
No, thanks.
Not sure from which perspective you're saying "No" from?
If you were a Twitter employee, that means quitting. But apparently from what you just said you don't want to lose your job. (There's no stress if getting fired is something that doesn't bother you)
Or from a management perspective? In which case I think vincnetas did a good job explaining why management might want to do this if they wanted to downsize.
Basically you're saying the concept of laying off people is a ridiculous viewpoint because it makes employees feel stressed. Sure this is just a discussion forum and we're all free to express opinions, but realistically, what makes you think an employee can say "No, thanks" to this?
Sure there is, long painful meetings where you go over your work for the last 30 days sounds miserable regardless of if you care about the outcome.
You also might lose your severance package.
While you can't say no thanks, if put in that situation by my employer I'd do the bare minimum and start lining up interviews with the tens of recruiters that message me daily (as I'm sure is the case for anyone with twitter on their resume)
Its not about “defending”, its about explaining. Even from your reply one can feel the instant defensive position you take when asked about (your) code. I think ability to disassociate from your code and just be able to discuss it (not defend) and explain what and why (tradeoffs) and how was done is very valuable in developer, and in anyone actually if you extend it beyond the code.
When take over a company ant talk with people and they take defensive position thats a red flag for me. (I take over companies in my head only so far)