Tech & AI

The radar's dashed target line is a commitment, not decoration — three prioritized gaps, each with a testable definition of closed.

Integer tail latencies are human constants: a periodic spike traced to a cache timeout hiding inside a rate-limiter plugin.

A Kafka consumer-lag alert that was really a terabyte of upgrade residue inside ClickHouse, detonated by a one-second background merge

"Familiar with Jenkins" is in every SRE job description, but writing pipeline scripts is not the skill. The skill is treating the delivery pipeline as a production system: idempotent procedures, observable job state, configuration in code — and knowing when automation itself becomes the new source of entropy. Grounded in a real Jenkins migration and its diagnose/fix script pairs.

Why the radar has nine axes — a capability model built on problem classes, not tool inventories, and where the moat actually is.

"Models are getting better, so the orchestration layer will disappear" is the same claim as "CPUs got faster, so the operating system will disappear." Faster CPUs did kill memory overlays and hand-rolled DMA — but process management, permissions and drivers got more important, not less. Orchestration isn't dying either; it's redistributing into three places. With a testable criterion for which is which.

A working harness that refactors SRE oncall triage from a human-executed procedure into an agent that investigates on its own while every irreversible action stays behind a deterministic gate. Built on four control primitives — Spec / Loop / Hook / Fork — with the reliability discipline of a Kubernetes control plane wrapped around a non-deterministic reasoning core.

好的 infra engineer 带来的不是「会敲命令」，而是在约束下做取舍的判断力。reconcile、IaC、冗余、降级、限流——现代大规模云管理的每一条方法论，本质都是在回答同一个问题：为了保住整体，你愿意主动放弃什么。

junior SRE 把 system metrics 和 app metrics 横着切，把 CPU 标出来就算监控。真正的转折是从上往下做——不同的主体关心不同的指标，每个主体的 SLO 不同，dashboard 也不同，而 dashboard 存在的意义是回答问题。

不背 K8s 概念,而是从'两个不可回避的事实'推导整个 K8s。子系统、resource kind、Operator 模式,全是必然推论而不是设计选择。