CI/CD has a “missing primitive”: toolchain + OS-level dependency management. We treat deps as “npm/pip/maven”, but then glue the real environment together with Homebrew/apt-get and end up with Bash embedded in YAML.
This issue argues that’s how you get commit-driven development: the only place the full environment exists is CI, so the feedback loop becomes commit → push → wait → read logs → repeat.
The piece maps the spectrum from asdf/mise (version pinning) → Devbox (shared dev shell + runnable tasks) → Nix (declarative, reproducible build graph), with a practical thesis: if you make the environment a first-class artifact, “local-first, reproducible pipelines” stop being aspirational and start being achievable. Includes a scorecard and concrete examples of flake-based CI patterns.
I am 47, I started with basic a TI99 4/A, I loved computers but I stopped at school when I was 15. At 30 I went back to evening classes and in 10 years I finished high-school and an IT degree while working full-time. I managed to get a job in Italy (I am Italian) but it was frustrating there that I emigrated to England. I have been hating my life and job since the superficiality and ignorance of people, all these horrible corporations using Java or .NET. On March I finished a contract and I cannot find another one, because of the changes in the IR35 law that the pathetic UK government made and the virus after. I was working only for the money, now everything is gone.
I am 47, too coward to kill myself, too terrified to take more shit.
This issue argues that’s how you get commit-driven development: the only place the full environment exists is CI, so the feedback loop becomes commit → push → wait → read logs → repeat.
The piece maps the spectrum from asdf/mise (version pinning) → Devbox (shared dev shell + runnable tasks) → Nix (declarative, reproducible build graph), with a practical thesis: if you make the environment a first-class artifact, “local-first, reproducible pipelines” stop being aspirational and start being achievable. Includes a scorecard and concrete examples of flake-based CI patterns.