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.
17 playbooks · 509 guides · 95 articles · 12 linked practice labs ·skip to practice
Fast pattern recognition for the production failures engineers see most often.
17 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.
Queue consumer not processing messages: how to debug it
Messages pile up in the queue but your consumer does nothing. The consumer might be crashed, stuck, or silently discarding messages.
JWT token invalid after deployment: how to debug it
JWTs work locally and in staging, but after a production deploy every token is rejected. The secret, algorithm, or clock changed.
Node version mismatch in CI: how to debug it
Your code uses a feature from Node 20 but CI runs Node 18. Build fails with a syntax error or missing API. The fix is one line in the CI config.
npm install works locally but fails in CI: how to debug it
npm install completes on your machine but CI throws errors. The issue is usually a clean environment gap: missing native build tools, lockfile drift, or platform-specific binaries.
File upload works locally but fails in production: how to debug it
Your upload endpoint works with local files but returns errors in production. The filesystem, permissions, size limits, or storage backend is different.
API returns 500 only in production: how to debug it
Your API endpoint returns 200 locally but 500 in production. Some code path that never triggers in dev fires in the real environment.
Long-form thinking on debugging habits, observability, and the systems around the bug.
How to Read Error Messages: A Debugging Protocol
Most engineers skim error messages and miss the signal. Here's a repeatable protocol for extracting maximum information from stack traces, log lines, and crash dumps — with a real incident walkthrough.
When to Escalate a Bug: A Decision Framework for Junior and Mid-Level Engineers
A practical framework for junior and mid-level engineers to decide when to escalate a bug, with real-world examples and criteria beyond time spent.
Debugging vs. Firefighting: Why Treating Production Incidents as Debugging Sessions Fails
When production goes down, your brain wants to debug. That instinct costs you hours. Here's why firefighting requires a fundamentally different approach, and the specific process I use to switch modes.
Writing an Incident Runbook That Actually Gets Used in Production
A runbook isn't a document—it's a tool. Here's how to write one that reduces MTTR and doesn't embarrass you during the next PagerDuty alert.
Debugging a production incident with your boss on Slack: staying rational when everything is on fire
A personal account of debugging a cascading Redis failure while the VP of Engineering watched, and the mental models that kept the fix from turning into a rollback.
Reading Distributed Traces to Find Latency: A Field Guide
Tracing tools generate a firehose of data. Here's how to filter the signal from the noise and actually find the root cause of high latency.