RWX on Changelog Master Feed

Hey, friends. I'm here with Dan Mangus, cofounder and CEO of RWX. Dan, what makes RWX and the way you're doing CI so different and interesting to our audience? You know, obviously, we're talking to you because we want to promote what we're doing. We want more engineers to become aware of what we're doing at RWX. But I think the thing that's interesting to me is that RWX is really kind of the first major evolution in CI and the approach for CI. And this is just highly relevant with with agentic driven coding. You know, CI has largely been the same since the advent of the practice, but these platforms were created when being able to run code in the cloud was really valuable. The fact that you could spin up virtual machines that would run some automation on a git push was, you know, really impactful for engineering teams trying to, like, build good developer processes and tools. But that's kind of the extent. What we've done in RWBYX is we've taken state of the art techniques used in build systems at organizations like Google and Meta. You know, Google has their internal build system Blaze, inspired the open source, Bazel, tool. But every engineering team I've talked to that wants to adopt Bazel has just found it extraordinarily difficult to use and configure. You have to have a dedicated engineering team to build and maintain the rules. It's hard to extend it to work with different types of languages and frameworks that engineering teams are looking to adopt. So it's been, you know, too prohibitive to actually adopt, you know, those technologies. But the ideas behind PASO are really impactful. They're similar to a lot of the ideas behind NICS. I would say NICS is kind of very similar, you know, in the difficulty to adopt. And effectively, what we've done at RWIs is we've taken those techniques, and we've made it very easy for engineers or agents to actually adopt and utilize, those, which namely are the automatic content based caching and the graph based task execution, which means that RWX eliminates all redundancy. You know, whereas other platforms are having to run the same setup steps on the same jobs, in every, you know, virtual machine that's spinning up. RWX can run the setup once on one machine and then fan out, accordingly based on just your dependency graph. So, effectively, with RWX, you never have to think about parallelization at all. You know, on other platforms, it's always like, well, do I add this onto the existing job? Do I make a new job for it? Do I have to duplicate all that setup? With RWX, you just define the task that you want to run and the dependencies between it, And we will run it with maximum parallelization based on your dependency graph.