Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Can someone help me understand why Twitter had not crumbled from the overwhelming weight of software decay after 50% of the staff was laid off? I’m not being sarcastic, it’s just honestly hard for me to understand…


People leaving doesn't cause decay. Decay happens over time - usually not just in a month.

People leaving means that there's nobody there who can fix the decay when it happens, though.


There's a number of plausible scenarios:

1. It takes more time for the rot to show.

2. Twitter devs were amazing at building really solid software

3. The culture of twitter was really that 1 person did the work and 9 others watched, enough of the productive devs stayed.

4. The effects of rot are overestimated.

I have no insight into how twitter worked as a company before Musk's takeover though, and I still think it is quite likely major problems will occur in the next couple of months.


Patience. It hasn't been long, and they probably left a test suite running under CI. Ideally it doesn't push to production without the tests passing and noone is left who knows how to disable it.


I mean, this test is really annoying and it's testing a case that I'll guarantee 100% won't happen often in production.


Did they ever disclose exact amount of engineers that were laid off? Twitter laid off lots of people but I doubt majority of them were engineers.


According to this: https://gizmodo.com/elon-musk-twitter-layoffs-engineering-sp... the first round of layoffs was around 40% engineers.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: