# runner Published articles for runner. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Super-comma-nix: A Rust helper for Nix shell and run commands with sandboxing DevFeed: [Super-comma-nix: A Rust helper for Nix shell and run commands with sandboxing]() Original publisher: [Read original article]() Author: ksvivek Published: 2026-08-14T08:01:27Z Content type: article Language: en Sources: [Announcements - NixOS Discourse]() Topics: [Nix](), [Rust](), [Command-line interface](), [Shell](), [ci]() Tags: [announcements](), [ci](), [code](), [command](), [commands](), [config](), [dependencies](), [developer-experience](), [environments](), [integrations](), [runner](), [rust](), [shell]() ### AI overview Super-comma-nix is a Rust command-runner helper for Nix that shortens common nix shell, nix run, and version-checking commands. It integrates with nix-output-monitor and landrun, supports configurable environment variables, and can produce commands without running them. ### Source excerpt Hi All super-comma is an ultra-fast, zero-dependency Nix command runner helper written in Rust and powered directly by nixpkgs-multiverse. It is inspired by the project comma nix. But my project is loaded with batteries and much more DX(Developer eXperience). You'll love it. This project makes the consumption easier for nix shell, nix run commands and versions list all with simple handy commands like ,(nix run) ,s(nix shell) ,v(versions checking) . The project have some cool flags and also integrations like nix-output-monitor and landrun for sandboxing all with just few flags. Dont want to type these nom and sandboxing flags verbose? U can add it to env variable for session or globally as like config. Go read the README, you'll love it. Though plenty of features, I sticked to this principle: Simple by default and powerful when needed So learn as u go. Want more integrations? Please feel free to raise an issue Sandboxing is pretty cool, u want to try a software but dont want it to connect to inernet? This project enables some real adhoc shell environments and with the sandboxing etc figure out the possibilities for everyday usage, CI etc The project has zero dependencies for rust. Coz this project just makes u type short commands and the program just does some splitting and joining of strings. So please feel free to unslop some logic written by the LLM there if u think it can be simplified. Skeptic coz LLM(though it'll change in future)? just use the program with -o flag and u can just use the program to give you the final command without running. The Github README is carefully crafted to explain all the features, so take your time there. I'm a nix and nixos user since 2024, so I know some nix and the project design and integration of nom and landrun etc purely my design and idea and instructed the llm with my knowledge. But i'm not having good rust knowledge, so that part is covered by LLM. I wanted to write it with PF languages like haskell etc, but I wanted to qui ## Performance engineering as a habit, not a project DevFeed: [Performance engineering as a habit, not a project]() Original publisher: [Read original article]() Author: fidelitas.io Published: 2026-05-16T16:00:00Z Content type: tutorial Language: en Sources: [fidelitas.io]() Topics: [Benchmark](), [ci](), [Code](), [systems]() Tags: [benchmark](), [benchmarks](), [build](), [ci](), [cloud](), [code-review](), [engineering-practice](), [git](), [hardware](), [latency](), [observability](), [performance](), [performance-engineering](), [regression](), [runner](), [slo]() ### AI overview The article argues that teams should treat performance engineering as a recurring engineering habit rather than a temporary project. It recommends measuring every pull request, comparing results with the previous day, and making performance regressions fail the build as part of CI. ### Source excerpt Most performance work is reactive: the bill goes up, the dashboard turns red, somebody opens an investigation ticket. Here's how to make it boring instead. ## JUnit Coroutines Runner DevFeed: [JUnit Coroutines Runner]() Original publisher: [Read original article]() Published: 2021-07-10T00:00:00Z Content type: tutorial Language: en Sources: [Vasya Drobushkov]() Topics: [Kotlin](), [Coroutines](), [Testing](), [Code]() Tags: [coroutines](), [junit](), [kotlin](), [kotlin-compiler](), [runner](), [suspend-function](), [tests]() ### AI overview This tutorial explores how to reduce repeated runBlockingTest setup in Kotlin coroutine tests by creating a custom JUnit rule. It explains the resulting suspend-function and bytecode validation issues and investigates their root cause. ### Source excerpt Introduction Recently while writing tests for kotlin code with coroutines I found one annoying thing: almost all the tests start with runBlockingTest. Typing the same stuff repeatedly is something we can't accept! So, I decided to think about how to improve this. Disclaimer. Yes, this is an example of how to spend few hours to optimize some task that requires you 2 seconds to complete each time. Even on a scale of hundreds of usages such optimization most likely won't pay your time back. But it is always fun to do some weird things even if you understand that they are stupid. ## Robust queue job handling in Craft CMS DevFeed: [Robust queue job handling in Craft CMS]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2019-08-03T15:37:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Content Management System](), [Job](), [async]() Tags: [async](), [avoid](), [cms](), [craft](), [failed](), [here-s](), [how-to](), [independent](), [insights](), [job](), [jobs](), [long-running](), [queue](), [runner](), [stalled](), [tasks](), [uses](), [using]() ### AI overview This tutorial explains how Craft CMS queues long-running tasks and why its default web-request-based queue execution can leave jobs stalled or failed. It discusses using an independent async queue runner. ### Source excerpt Craft CMS uses queue jobs for long-running tasks. Here's how to avoid stalled or failed queue jobs by using an independent async queue runner ## Guice Junit test-runner DevFeed: [Guice Junit test-runner]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2012-08-07T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [test](), [Maven Central](), [Code]() Tags: [article](), [build](), [code](), [dependencies](), [how-to](), [install](), [junit](), [maven-central](), [repository](), [runner](), [test](), [tests]() ### AI overview A tutorial on using a small Guice and JUnit test-runner library. Because the library was not yet published to Maven Central, readers must build and install it in their local repository before adding it as a dependency. ### Source excerpt Yesterday, I wrote a small article talking about Guice and JUnit, so, this time, I'll just say how to use the small lib that I build (not big deal, one class, one annotation =] )