Conference alert: The incredible @isaacvando from our team is organizing Software Should Work, an independent conference about software reliability, on July 16-17. ParadeDB is not affiliated, although we are proud sponsors. Speakers include the creators of Zig, SQLite, etc. More info: softwareshould.work/

Is there more to this race than having hot pools?

I'm enormously excited that Richard Hipp, the creator and lead maintainer of SQLite, will be speaking at Software Should Work. Join us on July 16-17!

Thrilled to have Andrew Kelley, creator of @ziglang speaking at Software Should Work. Early bird ticket sales end at midnight!

"RWX was built by engineers for engineers, and it shows in how fast and hands-off CI feels day to day." Learn how Tropic migrated from a bloated GitHub Actions workflow to RWX, cutting CI runtimes by 3x while accelerating the path from PR to deployment. rwx.com/customers/tropic

Unreal speaker lineup at this conference. I’m going.

Hot take 🔥: AI coding tools are about to make CI a big bottleneck in software development. We saw it before: AI → more code → code review became critical Now: AI → more commits → CI pipelines are collapsing AI coding agents require a new CI system.

You can build your own CI (this is impressive) or you can use RWX

“if someone else is always upstream, you can’t really redesign workflows or build anything that defensible”

Agree that CI as independent doesn’t make sense anymore. That is why RWX is so amazing with agents. Tell the agent to run RWX and when it finally does push the status check will instantly be green due to content-based caching.

When a flaky test fails on RWX, only 1 test needs to rerun instead of the entire shard. If you’re retrying an entire job on a failure, you’re doing it wrong.

Engineering practices are rapidly evolving with AI, and work-in-progress commits are now a thing of the past. rwx.com/blog/work-in-progres…

run `rwx run .rwx/ci.yml` and make sure CI passes and then commit and push

Software Should Work! But usually it's buggy and slow instead. That's why I'm organizing an independent conference on software reliability. Join us for Software Should Work on July 16-17 in Columbia, MO.

I hate this too. Which is why RWX does not work this way. Retrying any task in the graph while the other tasks keep running is a nice quality of life improvement.

Let AI iterate until CI passes, without having to commit and push. I'm excited to see this merged github.com/rwx-cloud/cli/pul…

Starting to wonder if I'll need to see this GitHub banner for the rest of my life. It's been there for months.

GitHub just shocked engineering team budgets with a change to GitHub Actions pricing. For people using self-hosted runners, or runners provided by a third-party, GitHub previously offered their CI/CD control plane for free. This will no longer be the case. Many people using third-party runners chose that option for the cost advantages, and this changes the equation. For engineering orgs that really want to reduce costs though, there’s a better way. GitHub Actions still uses the traditional approach of running jobs on parallel VMs. However, running pipelines as a graph (DAG), while utilizing automatic, content-based caching, provides the most substantial cost reductions. This approach is the key to how the big tech companies like Google and Meta run their pipelines. We built @rwx_cloud to make this approach accessible for regular engineering teams. RWX runs pipelines faster, and more cost effectively, than any other CI/CD platform. We completed a cost comparison today where a pipeline on RWX used a total of 84,004 seconds of execution, while the identical pipeline on GitHub Actions consumed 300,787 seconds of compute, for a 70% reduction on RWX. If anybody wants to relieve some pressure on their engineering budget in 2026, send me a DM.

"People can easily migrate CI elsewhere" – and there's no better place to migrate to than @rwx_cloud . It's the only platform that runs as a DAG with automatic content-based caching. Engineers love the performance and UX.