Field notes & guides.
For people running data centers, software and businesses
Practical guidance, new tools and lessons from the work. Choose an article, try what’s useful, and find a next step.
An unused Kubernetes volume isn't permission to delete it.
Kubernetes now exposes an unused-PVC signal. Turn it into an owned storage review, with retention and recovery checks, before treating it as a cleanup list.
↗Your inference benchmark changed. Did the system get faster?
Moving from GenAI-Perf to AIPerf? Align reasoning-token metrics before comparing inference latency, usable capacity or the case for more hardware.
↗Incremental Kubernetes backups need a tested restore path
Changing Kubernetes backup tooling? Check the changed block tracking API migration, retained recovery points, and application restore evidence before rollout.
↗JRuby vs CRuby performance: measure the work your application does
Compare JRuby and CRuby using separate startup and steady-state tests, verified output, memory limits and the same application workload.
↗Ruby concurrency: when to use threads, fibers, Ractors or processes
Choose a Ruby concurrency model by the work it must handle: waiting on I/O, using CPU cores, protecting shared state or isolating failures.
↗Rails memory keeps growing. Is it a leak, a larger workload or the worker layout?
Investigate Ruby on Rails memory growth with a repeatable workload, process-level measurements, GC counters and a clear test for retained objects.
↗Ruby on Rails on Omarchy: get the project running, not just Ruby
Set up an existing Rails project on Omarchy without confusing a global Ruby install, project dependencies and a production-ready application.
↗Test the workload before counting on Memory QoS
Kubernetes v1.37 changes Memory QoS defaults. A practical evaluation for data-center teams: check active policy, memory pressure, latency and useful output.
↗A service can be running before it's ready
For data-center and IT operators: separate process startup, readiness and recovery before the next restart sends work to a service that can't handle it.
↗24 open-source tools for Cloudflare work
Download 24 free MIT-licensed tools for Cloudflare Workers, D1, R2, email, releases, routes, tunnels, MCP and operational checks.
→Check Worker request policies before wiring them in
Download Worker No-Egress and Rate Limit Contract: two free local tools for testing outbound request policies and synthetic rate-limit responses.
↗Data-center power monitoring starts with a better handoff
DOE's oscillation-monitoring guidance raises a practical handoff question for data centers: what can the monitoring see, and who owns the gaps?
↗Email Fixture Lab: inspect an email file locally
A free CLI and local MCP tool for inspecting .eml structure, nested messages and reported delivery-status fields without uploading the message.
↗Karmada has graduated. Your failover plan still needs a rehearsal.
Karmada's CNCF graduation is a project milestone. Use this operator checklist to examine recovery capacity, application state, and failover evidence.
↗NVHBM changes the memory design. Start with the workload.
NVIDIA's NVHBM announcement raises a workload question: where is time actually spent? A practical evaluation plan for compute and data-center teams.
↗OpenTelemetry after graduation: write the incident path, not just the dashboard
Use OpenTelemetry's graduation as a reason to review one service's incident path: useful signals, Collector configuration, ownership, and response.
↗Three small Cloudflare tools, now open source
Download Worker Request Kit, Wrangler Config Doctor and Cloudflare Release Proof: three free v0.1 betas with public source.
↗Two more free tools for Cloudflare logging
Download OAuth Log Redactor and CF OTel Policy: two free, local-first beta tools for filtering JSON logs and configuring Worker logging policies.
↗Red Eagle Fenv and the 2006 Microsoft Accessibility Competition
The documented story of Red Eagle Fenv, Troy Mallory, the 2006 Microsoft accessibility competition, and the technical history still being recovered.
↗Why computers still waste time and energy.
Read the systems studies separately from Valen Systems' field notes.
→The Scheduler Can’t See the Work
Why a general-purpose scheduler sees runnable work but not the request, dependency, cache, or accelerator context behind it.
→An Idle CPU Isn’t Always the Right CPU
Why CPU placement has to account for cache, NUMA distance, capacity, and cooperating work instead of idle time alone.
→Migration Trades Locality for Balance
Why moving work can restore balance while discarding cache and memory locality that the task had already earned.
→Shorter Slices Don’t Create Free Responsiveness
Why responsiveness and throughput pull scheduler decisions in different directions.
→Fair CPU Time Isn’t Business Importance
Why fair-share accounting can’t by itself know which work matters most to a person or a business.
→History Arrives After the Work Changes
Why historical utilization is useful for prediction but can lag behind sudden workload changes.
→Looking for help with a system? Explore Valen Systems services
Earlier business-application writing
The systems articles are above. Our earlier work on customer operations and business applications remains available here.
Browse earlier business articles
Before you connect your inbox to your CRM
A practical inquiry-to-CRM handoff guide: define the record, owner, next action and failure cases before paying for an integration.
↗A Sitemap Is an Inventory, Not a Ranking Strategy
How sitemap families help search engines discover and classify pages, and why inclusion cannot make a weak page competitive.
↗Branded Search Is Proof of Identity, Not Proof of Market Position
Why ranking for a company name is different from ranking for a service, and what a local business must build to compete for non-branded demand.
↗Cloudflare Traffic Isn’t SEO Performance
Why edge requests, crawler activity, and internal tooling traffic cannot stand in for impressions, rankings, qualified visits, or leads.
↗Constant Crawling Didn’t Make the Site Rank
Why constant website crawling does not improve rankings, what a five-minute crawl loop actually proved, and how we rebuilt it around controlled releases.
↗The Client Should Own the Storefront, Not the Factory
A founder's field note on client website ownership and the boundary between contracted deliverables and reusable platform infrastructure.
↗What We Learned Building Local Service Pages Without Thin Content
A practical account of moving from city-and-service templates toward pages with real service detail, local proof, internal authority, and useful next steps.
↗