Engineering Reads — 2026-05-16#
The Big Idea#
The defining challenge of modern engineering is resource management at the extremes—whether that means reclaiming CI/CD compute cycles from vendor lock-in via lower-level orchestration, or driving down the inference costs of long-context LLMs through architectural optimization.
Deep Reads#
Slowly going mad with power using Tekton · xeiaso.net · Source The author outlines a strategic migration away from GitHub Actions to mitigate platform lock-in, replacing it with Tekton, a Kubernetes-native CI/CD operator. Instead of relying on a managed platform’s implicit state and runner lifecycles, Tekton forces you to model CI as a series of lower-level Kubernetes primitives: Tasks, TaskRuns, Pipelines, and PipelineRuns. This requires explicitly managing the grimy details of distributed builds, such as configuring Persistent Volume Claims (PVCs) for repository clones and shared Go module caches. The explicit tradeoff here is operational overhead—like debugging vague VCS errors or manually configuring Kaniko forks for Docker builds—in exchange for leveraging idle homelab compute and achieving absolute vendor neutrality. Engineers looking to future-proof their deployment pipelines against platform decay should read this to understand the true operational cost of infrastructure independence.