Elon Musk Twitter News: In a fresh development at Twitter, Elon Musk is asking for proof of work in the form of screenshots from engineers. This comes after firing Twitter employees for criticizing him publicly on social media. Earlier, Musk wrote to the employees saying they need to put in long hours with intense work. He also gave an option to quit with three months severance package. Following this, Musk attracted criticism from the Twitter communities as well as the employees.
In fact, some of the fired employees continue to openly criticize Musk for his style of managing the social media company.
As an engineer at Twitter, I can confirm that Elon Musk doesn’t understand anything about our website, or coding in general. Not gonna lie, we laugh REALLY hard about it behind his back. We’ve been calling him “the CEO,” but it stands for Code Efficiency 0.
— diana thirst (@rlycalm) November 15, 2022
Elon Musk Asks Screenshots From Twitter Engineers
In a latest, Musk wrote to the team of engineers about their ability to ‘actually write software’. If any of the engineers think they are capable, they should report before sending Musk a summary of achievements in last 6 months, as per an email from the Tesla CEO. According to a new email from Musk to the engineering team, the software engineers should submit 10 screenshots of the “most salient lines of code.” The email reads:
“Anyone who can actually write software, please report to the 10th floor at 2pm today. Before doing so, please email me a bullet point summary of what your code commits have achieved in the past 6 months”
On Thursday, the Twitter management informed employees that the offices were closed and badge access was suspended until Monday. This led to a lot of confusion among the employees. It is believed the offices were closed down to streamline the existing employees and their safeguard access to the software.
The presented content may include the personal opinion of the author and is subject to market condition. Do your market research before investing in cryptocurrencies. The author or the publication does not hold any responsibility for your personal financial loss.