我到底在怎么用 Claude Code
从 context-infrastructure 这个 repo 本身的三层记忆架构和路由表说起,到一套生产 oncall skill 的四条硬约束,再到从 gstack 批判性抄来的取舍,最后是一次对自己系统的六层诚实体检,全篇讲的是怎么用。
从 context-infrastructure 这个 repo 本身的三层记忆架构和路由表说起,到一套生产 oncall skill 的四条硬约束,再到从 gstack 批判性抄来的取舍,最后是一次对自己系统的六层诚实体检,全篇讲的是怎么用。
Audited a pager emitting ~960 OpsGenie alerts a day, ~85% of them default-P3, from 367 paging rules — traced four structural root causes, and rebuilt admission, dedup, and ownership so decay has to fight back against the system.
How the nine scores were derived from evidence density, what each one means, and a behavioral record that independently cross-checks the shape.
A self-authored, continuously running systemd-level daemon that turned Intel's Best Known Configuration from prose-and-shell documentation into a git-declared, continuously audited desired state across ~30 bare-metal servers spanning multiple clusters.
An Upgrade Safety System (check → plan → apply + evidence) turned an 18–21 hour, two-person manual ritual into a 6–8 hour single-operator procedure, executed across two production fleets with zero customer-impacting downtime.
A cross-tablet point-query index that prunes 566 tablets to about one before any tablet is opened, and a wide-read prefetch that removes serialization rather than IO — chosen because the cost of each was mostly avoidable fan-out, and shipped fail-open because neither may ever change a result. Includes the tradeoff that actually cost us, and the silent incident it caused.
Split, shed, then scale — and why the intuitive order takes the database down.
A new SQL statement inside the Apache Doris frontend that classifies every query heavy or light in 6–8 ms before execution — built on a fork, mechanism prepared for upstream, policy deliberately kept internal.
ClickHouse → Doris compute-storage separation: memory engineering, engine-level routing, two compaction incidents, and numbers that survived re-measurement.
Five design decisions behind a heavy-query compute pool that rests at zero: physical isolation instead of a workload class, discrete capacity instead of per-query autoscaling, sizing by bottleneck instead of by size, a controller reduced to patching one field, and a readiness path built on the assumption that every health signal eventually lies. Spot pricing is a per-pool consequence, not the point.