Ruby Rule in AI Coding Agents May Cut Script Token Usage by a Third

·5 views

Developer Lucian Ghinda published a post recommending that coding agents write all throwaway and utility scripts in Ruby, regardless of the project's primary language. His reasoning centers on code review: since he reads Ruby daily, agent-generated Ruby keeps him an active reviewer rather than a passive approver. A follow-up experiment by another developer tested whether the rule also reduces token usage, running Claude Opus 5 across four scripting tasks — log munging, config key renaming, file renumbering, and CSV transformation. The test compared outputs across Python, Ruby, Node, and bash arms under controlled conditions, requiring every implementation to produce byte-identical results before token counts were compared. Early findings suggested Ruby scripts were notably shorter, with the headline figure of roughly one-third fewer tokens, though the author acknowledges several methodological choices that could influence the outcome.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Engineer Replaces kube-proxy with eBPF in Homelab, Triggers 6-Hour Monitoring Blackout

A Kubernetes engineer running a four-node bare-metal homelab cluster upgraded Cilium from version 1.15 to 1.16 and enabled full eBPF-based kube-proxy replacement by flipping a single configuration flag. The change appeared successful at first, with all pods reporting healthy status, but at 2:47 AM an alert revealed that the SIEM had stopped receiving any network flow or Kubernetes audit log data. The root cause was that the eBPF datapath bypasses the iptables and conntrack layers that the security monitoring stack depended on to capture traffic. The engineer, who works with managed Kubernetes at Siemens professionally, documented the incident as a cautionary account of how replacing a core networking component can silently blind observability and security tooling. The episode highlights a broader gap in official documentation around eBPF adoption: tools built for the traditional netfilter universe do not automatically carry over into an eBPF-managed datapath.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Logic-based Sudoku solver cuts search nodes by 14,000x over basic backtracking

A developer benchmarked three Sudoku-solving strategies against the same engine and 40 identical puzzles to measure how much searching each approach requires. The naive backtracking method used in their shipped puzzle game averaged 28,835 search nodes per puzzle, while a most-constrained-variable (MRV) heuristic reduced that to 177. A logic-based constraint propagation solver went further, averaging just 2 nodes overall and only 3 even on Expert-difficulty puzzles. On Expert puzzles alone, the logic solver required roughly 34,000 times fewer search nodes than naive backtracking. The benchmark code is open source and fully deterministic, allowing anyone to reproduce the exact results by running a single command.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Builds VS Code Tool to Map Live Call Chains After AI Agents Break Contracts

A developer frustrated by AI coding agents silently breaking system contracts built Contour, a VS Code extension that automatically maps real-time call chains across Java/Spring Boot backends and React frontends. The tool addresses a common problem where agents or humans edit one side of a codebase without knowing downstream dependencies exist, such as scheduled jobs, Kafka events, or chained service calls. Contour reads source code directly to reflect how a system actually connects at any given moment, rather than relying on outdated documentation or diagrams. It surfaces inline CodeLens annotations in the editor gutter, showing which frontend calls hit which controller endpoints and vice versa, with explicit warnings when no caller or handler is found. A companion tool called Contour MCP was also built to let AI agents query the call-chain map directly, rather than operating with only single-file context.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Diagnose and Fix a Slow WooCommerce Checkout Page

WooCommerce checkout pages are excluded from page caching by design, making them uniquely vulnerable to performance issues that standard caching plugins cannot address. Tools like Query Monitor can identify the root cause by revealing total query counts, query times, and the specific plugins responsible for excessive database calls. Common culprits include shipping plugins making live carrier API calls on every update, unnecessary cart fragment requests, synchronous calls by analytics and marketing plugins, and bloated autoloaded data left behind by old plugins. Installing an object cache solution such as Redis or Memcached can significantly reduce repeated database hits on these dynamic pages. If application-level fixes fail to improve checkout speed, the bottleneck likely lies at the hosting level, including PHP version, worker count, or shared server resources.

0 comments Read more at DEV Community