Former employees say Twitter is stuck in a recurring code loop nightmare

Love this bit: :"...But it requires regular checking by staff, and institutional knowledge of how Twitter’s codebase works..."

More like knowledge of how "job security through complexity" was institutionalized into the codebase.

I'm watching with popcorn to see if Twitter catches fire completely or Musk puts out the flames by pissing on the entire codebase (sorry for the visual) but I'm not sure these articles are meant for anyone other than former employees who're still mad about the changeover.

I still can't believe that twitter never had a dev/test environment.

I mean, what's the VP engineering's excuse for that, they didn't have enough Aerons to build a real dev/test environment?

What about documentation and process? Not enough 10k espresso machines?

This was a public company, after all.

We can only hope that the next time it goes down, it never comes back online.

This lines up with predictions of an April disaster for Twitter.