Ideas for building
better software.

One command for 13 AI coding-assistant context files

Every AI coding tool wants a file describing your project. Claude Code reads CLAUDE.md. Cursor reads .cursor/rules. Then there's AGENTS.md, GEMINI.md, Copilot instructions, Aider's CONVENTIONS.md, Windsurf, Cline, Continue, Kilo Code, Trae, Junie, Warp... Same content, a dozen names and formats. Maintaining them by hand is busywork, and the second your stack changes they're stale. npx @horiastanxd/claude-init It analyzes the repo once - language, framework, package manager, scripts, file tree,

Kubernetes Observability

Originally published on lavkesh.com I've found that Kubernetes observability is a unique beast, different from monitoring your application, you're dealing with infrastructure, workloads, and the cluster itself, but fortunately the tooling has come a long way so you don't have to start from scratch Prometheus is the de facto standard for Kubernetes, its pull model fits naturally with Kubernetes service discovery, you add annotations and Prometheus automatically finds your pods, no manual configur

From Silos to Service Topology: Why Netflix Built a Real-Time Service Map

VMAF v1: Good Is Not Good Enough

AI Agents For Release Notes And Changelog Automation

Here's a changelog entry nobody asked for: ## v2.4.0 - fix stuff - wip - address PR comments - Merge branch 'main' into feature/checkout - update deps - final fix (for real this time) That's not a changelog. That's a git log with a version number stapled on top. And the people who maintain Keep a Changelog have a name for it that I can't improve on: "Don't let your friends dump git logs into changelogs." The interesting part is the timing. That tagline is from 2014. The problem of turning raw

Scarab Diagnostic Field Test #034 - Prometheus Docker Swarm Label Source Boundary

Target: prometheus/prometheus Issue: prometheus/prometheus#12244 Pull request: prometheus/prometheus#18979 Field Lab record: Prometheus #12244 This field test was about documentation, but not "just documentation." The public issue reported confusion around Docker Swarm task discovery metadata in Prometheus. The user expected __meta_dockerswarm_container_label_<labelname> to expose labels from the running container or image, such as OCI image labels. The visible behavior was different. The metada

Scarab Diagnostic Field Test #033 - Prometheus Remote-Write Label Order Boundary

Target: prometheus/prometheus Issue: prometheus/prometheus#11505 Pull request: prometheus/prometheus#18978 Field Lab record: Prometheus #11505 This field test was about a small but important remote-write boundary in Prometheus: labels are required to be sorted lexicographically, but incoming remote-write labels could pass through a conversion path before that requirement was enforced. That sounds narrow because it is narrow. But this is exactly the kind of case Scarab is meant to make visible. N

Iran requires insurance on ships using Strait of Hormuz, fees likely to follow

Comments