Ever worked somewhere where all the good devs have left and it's outsourced to a bunch of cheap labour? They find ways to keep it running for years. Maybe not doing the way you'd like (log rotates are stuck? Better turn off the logging system), but they make it work. Ops people like to overestimate their own importance like everyone else.
> So how, in some detail, do we get from big-ass mixture model of transformers to even self-operation? That’s got to be a pre-requisite for self-improvement right?
No? Model could propose a bunch of changes to its own code and let the human developers take care of deploying it. Of course the developers could theoretically review those changes carefully... but let's be real, they won't. In the worst case a human-level-intelligent AI could certainly email the outsourced ops staff and ask them to deploy tag x. More generally, it can just do whatever a new dev would do - read your wiki and figure out which commands to run from that. If there's an error, look up old email threads on it, or similar errors online, or try to match up a traceback against source code and look for common errors. We expect fresh grads to do this stuff all the time, it's really not that hard.
> Then there’s the reality of AI development thus far, which is that it comes in stops and starts. Clearly the past is no guarantee of the future, but it seems a damned sight better as a prior than the log scale and a ruler methodology employed by Yud or whoever.
WTF kind of logic is this? Daily weather goes up and down, so clearly extrapolating any kind of long-term trend in temperature is silly.