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.
Express-Session Not Saving Between Requests: The Real Causes
A debugging guide for when express-session fails to persist session data across HTTP requests in Node.js applications.
Node.js Heap Snapshot Analysis: Finding the Leak That Survived GC
A practical guide to analyzing Node.js heap snapshots to find memory leaks that survive garbage collection. Covers snapshot comparison, retaining paths, and hidden class instances.
Node.js Module Resolution: Why 'Cannot Find Module' Keeps Happening
A practical debugging guide for Node.js 'cannot find module' errors, covering real-world causes like path aliases, hoisting edge cases, and missing native addons.
Express req.body Undefined: Body-Parser Not Working
Debug why Express `req.body` returns undefined even after installing body-parser. Covers middleware order, missing Content-Type, and URL encoding issues.
Debug Node.js child_process.spawn() Failures
A direct guide to diagnosing and fixing ENOENT, EPIPE, and silent failures in child_process.spawn().
Node.js Worker Threads Messages Not Received: Debugging Communication Failures
A practical guide to debugging messages that never arrive between Node.js main thread and worker threads, covering postMessage timing, cloning errors, and port exhaustion.
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.