News for hackers. Stuff that matters.
Re:If you (still) work at Twitter and you can code, head to ... by piva00 on Friday November 18, 2022 @02:13PM (#33660403)
Yes, of course they did: design docs, RFCs, some PoCs to validate assumptions on small scale, etc. that's all part of a staff engineer job.

Now the question is: does Elon have enough technical expertise (or access to such) to be able to judge if a collection of assorted 10 screenshots without context of some GDoc pages, some shoddy PoC code and comments on RFCs is up to par with his bar of what a Staff Software Engineer title should produce? I highly doubt it.

It's not about showing evidence of work, it's that technical work can differ so much depending on context and constraints that it's impossible to demonstrate its value in such a reductive way, it's simple and clear stupidity to even ask to be demonstrated that way.

Re:If you (still) work at Twitter and you can code, head to ... by khazhoux on Friday November 18, 2022 @03:00PM (#33661178)
I’m actually not defending Elon. A blanket “show me ten git snippets” is dumb. This is a horrible way to start off as new boss. I’m only saying, there’s way too much apologism in this thread for not having tangible work results.

To your point, if I started as new manager for a team and the TL said they mostly wrote RFCs and design docs, my next question would be whether those docs led to an actual implementation (by orher people is ok). IF it turned out they write go-nowhere docs and sit in meetings giving obvious advice all day, then I’ll flag it as a potential problem that needs deeper investigation.