编程开发

on-call readiness; documentation/runbooks.

Reviews a design doc for gaps and risky assumptions before implementation — cheaper than discovering them mid-build.

Converts vague "tech debt" complaints into a ranked, quantified backlog linked to business risk and remediation cost.

Sequences a migration with risk control: inventory, patterns, data movement, cutover rehearsals, and rollback.

Defines SLOs, error budgets, alerting, and dashboards for a service from user journeys — symptom-based alerting, not noise.

Designs search (ES/OpenSearch/vector/hybrid) with relevance tuning pipelines — includes ranking eval and zero-result handling.

Designs reliable uploads for large files with virus scanning, image/video processing, and storage lifecycle.

Designs limiters (per-user/IP/tenant/API key), algorithm choice, and 429 contracts — including distributed counters and fairness.

Designs layered caching with explicit invalidation and consistency contracts — the hardest part of real systems.

Designs reliable event flows (Kafka/RabbitMQ/EventBridge): contracts, ordering, duplicates, sagas, and read models — including when NOT to use events.

Selects and details an isolation model (shared DB / schema per tenant / DB per tenant) against real requirements, including noisy-neighbor and backup isolation.

Forces contract design before implementation, with evolution/versioning rules and consumer review — prevents costly API mistakes.

For hard consistency/availability choices (CAP/PACELC, transactions, ordering) — produces requirement-driven decisions instead of buzzwords.

Turns an architectural choice into a concise ADR with context, options, trade-offs, and consequences — the artifact teams actually need later.

Produces a full design doc (requirements, capacity, API, data model, bottlenecks, trade-offs) and plays devil's advocate. Works for interviews and real projects.

about it, and pointers to 2 concepts worth studying next (with canonical links).…

construct, explain WHAT it does and WHY this pattern exists, plus the cost or pitfall it…

Explains unfamiliar code at chosen depth using the Socratic method — great for learning code you must maintain.

formatting churn, unrelated files, secrets) before finalizing.…

migration/rollback notes, test evidence, and a checklist (tests, docs, flags).

docs/test/chore with scope!), each atomic with body explaining WHY and a BREAKING CHANGE…

Writes Conventional Commits, PR descriptions, and user-facing changelogs from a diff — useful when preparing releases.

ask which is correct rather than guessing.…

invariants, and a 10-line usage example; architecture note only where non-obvious. 4.…