cnunciato
Emulating Terraform on Pulumi's Engine
Compatibility Testing Pulumi HCL
A guided tour of Terraform state, hosted modules, and HCL in Pulumi
Pulumi Do: Direct Resource Operations for Any Cloud
Better CLI Interactions for Agents and Humans
How We Built a Distributed Work Scheduling System for Pulumi Cloud
How to use AI with expressive writing without generating AI slop
Speeding up Pulumi Operations by up to 20x
Pulumi for All Your IaC – Including Terraform and HCL
Designing log-navigation tools in the Buildkite MCP server
What's new in the Buildkite MCP server
(Re)Building Reddit Mobile CI in 2025
I love this. It's exactly how I feel when I read AI-generated content. A little bit sick, not really sure why.
The sneaky costs of CI apathy, and what top teams do about it
Dynamic Pipelines with Bazel and Buildkite
A Guide to Bazel Query
Understanding the SLSA Framework
Scaling Faire's CI Horizontally with Buildkite and Kubernetes
For one, with GitHub Actions, hosted and self-hosted runners are fundamentally different applications; hosted runners are fully configured container images, (with base OS, tools, etc., on board), whereas self-hosted runners are essentially thin, unconfigured shell scripts. This means that unless you're planning on using self-hosted runners in production (which some do of course, but most don't), it wouldn't make sense to dev/test with them locally, given how different they are. With Buildkite, there's only one "way" -- `buildkite-agent`, the single binary I linked to above.
The connection models are also different. While both GHA self-hosted runners and the Buildkite agent connect to a remote service to claim and run jobs, GHA runners must first be registered with a GitHub org or repository before you can use them, and then workflows must also be configured to use them (e.g., with `runs-on` params). With Buildkite, any `buildkite-agent` with a proper token can connect to a queue to run a job.
There are others, but hopefully that gives you an idea.
This is one thing I really love about Buildkite[0] -- being able to run the agent locally. (Full disclosure: I also work for Buildkite.) The Buildkite agent runs as a normal process too (rather than as a Docker container), which makes the process of workflow development way simpler, IMO. I also keep a handful of agents running locally on my laptop for personal projects, which is nice. (Why run those processes on someone else's infra if I don't have to?)
>Reusability and YAML
This is another one that I believe is unique to Buildkite and that I also find super useful. You can write your workflows in YAML of course -- but you can also write them in your language of choice, and then serialize to YAML or JSON when you're ready to start the run (or even add onto the run as it's running if you need to). This lets you encapsulate and reuse (and test, etc.) workflow logic as you need. We have many large customers that do some amazing things with this capability.