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.
Cron job not running in production: how to debug scheduled tasks
Your cron job runs fine when triggered manually but never fires on its schedule in production. The scheduler, timezone, or environment is wrong.
Worker process memory leak: how to find and fix memory leaks in background jobs
Your background worker's memory usage grows steadily until it crashes. The leak is accumulating across jobs — each job leaves something behind.
Rate limit bug: how to debug unexpected rate limiting issues
Legitimate users are hitting rate limits. The limiter is too aggressive, counting wrong, or sharing state across instances when it should not.
Request body undefined in Express: how to debug missing request bodies
Your Express route handler receives `req.body` as `undefined` or an empty object. The body parser is missing, misconfigured, or not matching the content type.
ESM CommonJS import error: how to debug module system conflicts
Your import breaks with 'require is not defined' or 'Cannot use import outside a module'. The file is being treated as the wrong module system.
GitHub Actions missing secret: how to debug CI secret issues
Your GitHub Actions workflow references a secret that does not exist in the repository settings. The workflow fails with an empty value or an error.
Long-form thinking on debugging habits, observability, and the systems around the bug.
Debugging Production Issues Without a Debugger: Approaches That Work
Attaching an interactive debugger in production is usually impossible. Here’s how I gather signal, reproduce issues, and restore service using other techniques.
Writing Bug Reports That Developers Appreciate
A good bug report is more than a template. Learn which details actually move the needle, and which common 'best practices' waste developer time.
Assert Statements: Where They Help and Where They Hurt
Assert statements are a double-edged sword. Used correctly, they catch bugs early and document invariants. Used carelessly, they can mask failures and create security holes. Here's how to wield them effectively.
Defensive Logging: Patterns for Surviving Production Data Rot
Most logging advice stops at 'log more'. Here's how to log defensively—handling nulls, encoding, PII, and context propagation before they rot your observability pipeline.
Debuggers vs Console.log: Why I Stopped Using Print Statements for Debugging
Print statements are the duct tape of debugging. They work for trivial issues, but for race conditions, async flows, or deep call stacks, a debugger saves hours. Here's what I learned after years of using both.
Treating Bugs as Hypotheses: How the Scientific Method Fixes Debugging
Frustrated by flailing through logs? The scientific method turns debugging into a reproducible process. Here's how to formulate hypotheses, design experiments, and isolate root causes with confidence.