Live data from Hacker News

If you (still) work at Twitter and you can code, head to the HQ now

theverge.com

681–683 of 683 posts

Re: If you (still) work at Twitter and you can code, head to the HQ now

#681

Earlier quoted context omitted.

It's literally just some bizarre hazing ritual. Trying to evaluate whether code is good or bad from some screenshots without understanding the context and being familiar with the codebase makes no sense anyway. Anyone can show you ten screenshots of formally well written code and you have no idea whether it's useless or not.

I think the only reason is to figure out if people are working. Any dev I could think of doing their actual job can take 10 screenshots and point what they worked on in the last 6 months. It would be insane if they couldn't.

Including PEs and Sr.PEs? If they're coding, it's usually a detriment to the business unless they are extremely specialized and possess some blend of skills that allow them to take on tasking that cannot be delegated to others. I'm mostly talking about top companies where those titles are hard-earned and are associated with very broad impact.

Re: If you (still) work at Twitter and you can code, head to the HQ now

#682

Earlier quoted context omitted.

He's not doing anything unusual - he's just doing ti very aggressively and quickly. He dropped the bottom 50% as reported on by managers and now he has identified the best of that 50% and asked everyone else to either commit or get out. This is standard operating procedure but it is usually done over the course of many months to over a year instead of like 1 month in this case. If it works then I think senior manager…

Do you really think you can layoff just the bottom 50%?

Seems to be working so far.

Re: If you (still) work at Twitter and you can code, head to the HQ now

#683
post #259

Earlier quoted context omitted.

The IT department might have sent the email, not Elon himself...

Anybody competent in IT wouldn't be asking for screenshots of code. They'd know how to access the repos touched by a given user.

That wouldn't be relevant if it were for entrapment purposes, would it?
Post reply on HN