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 · 512 guides · 97 articles · 13 linked practice labs ·skip to practice
Fast pattern recognition for the production failures engineers see most often.
0 playbooks in Debugging Craft
No playbooks found
Nothing matches “”. Try a broader term.
Service reliability · from symptoms to evidence
Microsoft 365 outage debugging
Separate Outlook symptoms from service impact, understand Graph retry timing, and follow queued email through acceptance and delivery. Read the guides, then practise the failure patterns in two simulated labs.
Structured investigations for the failure modes engineers meet in real systems.
Angular Standalone Component Import Error: What Actually Works
A debugging guide for Angular standalone component import errors – the import-not-found and unexpected directive issues you hit in real projects.
Angular Signals Not Updating the Template: Debugging Guide
A practical guide to debugging Angular Signals that fail to trigger template updates. Covers change detection, signal creation, and common pitfalls.
Angular HTTP Interceptor Not Firing: Real Causes and Fixes
Is your Angular HTTP interceptor silently failing? This guide covers the non-obvious reasons—from provider scoping to AOT issues—with concrete commands to verify.
ASP.NET Core Captive Dependency Scope Error: Diagnosis and Fixes
A practical guide to diagnosing and fixing captive dependency scope errors in ASP.NET Core DI, with real-world commands and code patterns.
Android ANR (Application Not Responding) Debugging: From Input Dispatch to Watchdog Timeouts
A field guide for Android engineers on diagnosing and fixing Application Not Responding (ANR) errors, covering input dispatch, broadcast receivers, and service timeouts.
Flutter setState Not Rebuilding Widget – Debugging Stale UI
Diagnose why setState doesn't trigger a rebuild in Flutter: missing context, wrong state class, or identity issues. Includes concrete commands and fixes.
Long-form thinking on debugging habits, observability, and the systems around the bug.
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.
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.