"A fix is imminent", the press release from Google says; "we've got our best programmers on it."
And they have. But the programmers in question have never touched this system before. It was vibe-coded on the cheap by a contracting company which has since dissolved. All the function names look helpful, but do something slightly different to what they claim.
A simple rollback to the previous version of the code was the first suggestion, of course. But the last deployment was a month and a half ago. It was working fine, until it wasn't.
"We could just rip this whole module out," someone suggests. But it needs to correctly encode the TLA details in the WTF wrapper, otherwise everything five steps down will break. And none of this is documented anywhere.
Do they continue trying to trace the source of the problem, or do they just rewrite the whole damn thing? Tensions are rising. Management is throwing a fit, obviously, and the programmers are not immune to the affects of the outage themselves. They have friends and family-- some of them vulnerable-- who are starting to worry about how long they'll have to go without vital goods and services.
3/4
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.