The author expresses a strong dislike for GitHub Actions, comparing it unfavorably to previous technology experiences. This disdain stems from a recent frustrating episode while working on a project called tmplr, which involves creating template files for projects. The author had set up a build process using a tool called CUE within a file named build.rs but encountered failure during Continuous Integration (CI) because CUE was not properly installed for the Linux ARM platform. Despite successful builds on other platforms, the isolation of the cross-building process in GitHub Actions led to this issue. The author describes a tedious feedback loop that resulted from trying to fix the CI build. Each change required multiple steps, including searching for solutions, editing configuration files, and waiting for builds to complete—often taking 2-3 minutes per iteration. This inefficiency felt akin to using outdated technology, like saving in a slow editor or pushing commits with a cassette tape. Ultimately, after spending about 30 minutes in this loop, the author decided to abandon the build.rs approach entirely, moving the logic to a GNU Makefile instead, which resolved the issue. The article highlights how GitHub Actions can hinder productivity, especially when debugging or optimizing builds. Despite the frustrations, the author acknowledges some benefits of the platform, like ease of setup for macOS builds. However, the overall sentiment is one of exasperation, as the author feels trapped in a system that complicates rather than simplifies the development process.