Anita Zhang

I mean, I'd say meta is like super into, you know, release frequently. And so if we always stick to like upstream, then we'll always get like the newest stuff and we're less likely to run into some obscure bug from like two years ago that is really hard to debug.

I mean, I'd say meta is like super into, you know, release frequently. And so if we always stick to like upstream, then we'll always get like the newest stuff and we're less likely to run into some obscure bug from like two years ago that is really hard to debug.

Yeah, so it's mainly the major upgrades that take up to a year. So, you know, when we're about to go from 9, CentOS stream 9 to 10, that will probably take a long time than if we were just doing like our rolling OS upgrades. So the thing about CentOS is that we do maintain kind of like ABI boundaries. So we expect that the changes that, you know, Red Hat and CentOS are making.

Yeah, so it's mainly the major upgrades that take up to a year. So, you know, when we're about to go from 9, CentOS stream 9 to 10, that will probably take a long time than if we were just doing like our rolling OS upgrades. So the thing about CentOS is that we do maintain kind of like ABI boundaries. So we expect that the changes that, you know, Red Hat and CentOS are making.

Two packages are mostly like bug fixes that won't break compatibility in the program. And that's remained true. We haven't run into a lot of major issues with rolling OS upgrades. Most issues come from like when we personally are trying to pull in like the latest version of system D or something and we're rolling that out. Those we have to do with more intention.

Two packages are mostly like bug fixes that won't break compatibility in the program. And that's remained true. We haven't run into a lot of major issues with rolling OS upgrades. Most issues come from like when we personally are trying to pull in like the latest version of system D or something and we're rolling that out. Those we have to do with more intention.

Yeah, I'm probably not the best person to ask about it, but we do have a pretty sizable team now of production engineers dedicated to supporting the AI fleet and making sure that it's stable and that our train jobs don't crash and things like that.

Yeah, I'm probably not the best person to ask about it, but we do have a pretty sizable team now of production engineers dedicated to supporting the AI fleet and making sure that it's stable and that our train jobs don't crash and things like that.

It's more like the latter. So even though everything's in TW Shared, we know what kind of machine type they are. So you can specify what purpose you're using the machine for and things like that.

It's more like the latter. So even though everything's in TW Shared, we know what kind of machine type they are. So you can specify what purpose you're using the machine for and things like that.

Well, I'm a software engineer technically, I guess.

Well, I'm a software engineer technically, I guess.

I'd say production engineer and software engineer are the most similar, especially in infrastructure. When I was in the containers team, the production engineers and software engineers pretty much all just did the same stuff. Like we were all just focused on scaling and making the system more reliable.

I'd say production engineer and software engineer are the most similar, especially in infrastructure. When I was in the containers team, the production engineers and software engineers pretty much all just did the same stuff. Like we were all just focused on scaling and making the system more reliable.

I'd say in like a product team, production engineers focus more on operationalizing and making the service production ready while the software engineer is kind of like creating new features and things like that.

I'd say in like a product team, production engineers focus more on operationalizing and making the service production ready while the software engineer is kind of like creating new features and things like that.

Yeah, I mean, I probably dispute the fact that people have to understand kind of like the internals of how the hosts and things are laid out. So the majority of services, we're talking like millions of hosts and TW shared, they are running containers.

Yeah, I mean, I probably dispute the fact that people have to understand kind of like the internals of how the hosts and things are laid out. So the majority of services, we're talking like millions of hosts and TW shared, they are running containers.

And I'd say a lot of their knowledge about the infrastructure probably stops at when they write the job spec and to the point where they go into the UI and look at the logs. So if you're just writing like a service, a lot of that's abstracted away from you. You don't even have to handle like load balancing and stuff. There's like a whole separate team that deals with that as well.

And I'd say a lot of their knowledge about the infrastructure probably stops at when they write the job spec and to the point where they go into the UI and look at the logs. So if you're just writing like a service, a lot of that's abstracted away from you. You don't even have to handle like load balancing and stuff. There's like a whole separate team that deals with that as well.