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.
React setState Called but State Not Updating: Real Debugging Steps
React state not updating after setState? Pinpoint hidden causes—like stale closures, async timing, or skipped re-renders—using targeted debugging tactics.
React.memo Fails to Prevent Re-render: Deep Props, Functions, and Traps
Debug React.memo not working: identify why supposedly memoized components still re-render, including deep prop equality, unstable functions, and context pitfalls.
Diagnosing 404s from Next.js API Routes That Should Exist
When your Next.js API route responds with a 404 despite existing, dig past simple typos. This guide covers real fixes, pitfalls, and non-obvious causes.
Next.js Middleware Not Executing on Expected Routes
Investigate why your Next.js middleware isn't firing as expected. This guide goes beyond basics and addresses subtle config, routing, and deployment issues.
Environment Variable Undefined at Runtime in Next.js Projects
Why and how Next.js environment variables end up undefined during runtime, including hidden build pitfalls. Step-by-step debugging for real production issues.
Diagnosing ‘React Hook Called Conditionally’ in Function Components
A hands-on guide to resolving errors from calling React hooks inside conditional blocks. Covers root causes, real-world mistakes, and validation steps.
Long-form thinking on debugging habits, observability, and the systems around the bug.
Sentry Error Monitoring: A Practical Setup Guide from a Production Outage
A step-by-step setup guide for Sentry error monitoring, covering source maps, release tracking, grouping rules, and alerting — with a real story of a production outage that taught us the hard way.
Reading Prometheus Alert Rules: A Practical Reference for Debugging Firing Alerts
Alert rules look straightforward until you're staring at a firing alert at 3 AM. This post covers the structure, common traps, and how to extract actionable intent from any rule.
Debugging Network Issues with Chrome DevTools: Timing, Waterfalls, and Hidden Columns
A practical guide to diagnosing slow requests, stalled connections, and caching bugs using the Network tab's non-obvious features.
Finding Jank in React Apps with Chrome DevTools Performance Tab
A practical walkthrough of the Performance tab for diagnosing frame drops and long tasks in React apps, with a real debugging story.
Using Breakpoints Effectively: Beyond Step and Continue
Most engineers know F9 to set a breakpoint and F5 to run. But breakpoints have hidden superpowers — conditional, logpoint, hit-count, and data breakpoints — that can cut debugging time in half. Here's how to use them with real examples.
Conditional Breakpoints: When and How to Use Them Beyond the Basics
Conditional breakpoints stop only when a specific condition is true, reducing noise in loops and high-frequency code. Here's how to wield them in Chrome DevTools, VS Code, and IntelliJ, plus a war story about a subtle race condition.