Buglyst Blog
Learn to debug under pressure.
Playbooks for fast pattern recognition, guides for the full investigation, and articles for the engineering judgment around the edges.
18 playbooks · 509 guides · 96 articles · 13 linked practice labs ·skip to practice
Fast pattern recognition for the production failures engineers see most often.
18 playbooks
Debugging Env Var Issues
A concise checklist for incidents where local works but CI, staging, or production changes behavior.
Debugging Cache Stampedes
How to recognize and contain request spikes when cached data expires.
Debugging CORS Origin Bugs
A practical way to inspect origin parsing, credentials, and header behavior.
Debugging Retry Bugs
Retry issues often hide the first failure and create duplicate work.
Debugging Timezone Bugs
Time bugs usually live at day boundaries, DST changes, and unit conversions.
Debugging Pagination Bugs
Pagination bugs hide in boundary math, cursor reuse, and new records arriving between pages.
Structured investigations for the failure modes engineers meet in real systems.
Pulumi State Drift: How Refresh Lies and What to Actually Do
A hard-nosed guide to diagnosing and fixing Pulumi state drift when `pulumi refresh` doesn't behave as expected. Covers real root causes, verification steps, and a war story from production.
Ansible Task Not Idempotent: Changed Every Run
An Ansible task that reports 'changed' on every run is breaking idempotency. This guide covers real-world causes beyond check_mode, from missing diff to transient state in shell commands.
Istio Sidecar Envoy 503: Debugging Upstream Connection Failures
A systematic guide to diagnosing 503 responses from Istio sidecar proxies, covering upstream cluster issues, TLS mismatch, and routing misconfigurations.
Linkerd mTLS Handshake Failures: A Practical Debugging Guide
Linkerd mTLS connections failing? This guide covers diagnosing broken TLS handshakes, certificate mismatches, and policy misconfigurations in Kubernetes.
Debugging SWC Transform Errors: Syntax Errors in Rust-Based JS/TS Transforms
A practical guide to diagnosing and fixing syntax errors when using SWC for JavaScript/TypeScript transforms. Covers common causes like mismatched decorators, unsupported syntax, and misconfigured .swcrc.
Metro Bundler 'Unable to Resolve Module' — Real Debugging & Fix Strategy
A practical guide to debugging Metro Bundler's 'Unable to resolve module' errors in React Native projects, covering cache, aliases, symlinks, and native module misconfigurations.
Long-form thinking on debugging habits, observability, and the systems around the bug.
Why Your P99 Latency Is Lying to You (and What to Use Instead)
The 99th percentile is the go-to metric for tail latency, but it's easy to fool. Here's a real outage caused by trusting P99, and how to build a more honest monitoring stack.
The Real Cost of N+1 Queries: More Than Just Slow Pages
N+1 queries are often dismissed as a minor performance issue, but their real cost goes far beyond slow page loads—think cascading timeouts, database meltdowns, and cloud bills that balloon overnight. Here's what you're actually paying for.
Reading Flame Graphs: The Non-Obvious Patterns That Reveal Real Bottlenecks
Flame graphs are everywhere in performance profiling, but most engineers only scratch the surface. Here are the patterns that actually tell you where your code is slow.
Print Debugging vs Debugger: When printf Wins and When It Fails
Printf debugging is dismissed as primitive, but in many real-world scenarios it's faster and more reliable than a full debugger. Here's the tradeoff with concrete examples from distributed systems and production incidents.
Writing Postmortems That Actually Improve Reliability
A postmortem that blames someone gets filed and forgotten. A postmortem that traces cause without blame becomes a reliability upgrade. Here's how to write the second kind, with a real example from an 18-hour DNS outage.
Feature Flag Debt: When Your 500 Conditional Branches Become the Incident
Feature flags are great until they're not. Here's how to audit, remove, and automate cleanup before your 500th conditional branch becomes the root cause of a production incident.