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 Security & Auth
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.
Supabase Auth Not Working: Session, Redirect, and JWT Debugging
A hands-on debugging guide for Supabase auth failures—session drops, redirect loops, and JWT validation errors in production.
Passport.js Strategy Not Authenticating: A Diagnostic Walkthrough
Step-by-step guide to debug a Passport.js strategy that silently fails to authenticate, covering serialization, middleware order, and callback pitfalls.
bcrypt.compare() Always Returns False: A Field Guide
Debug why bcrypt.compare() always returns false. Covers salt rounds, encoding mismatches, and truncated hashes with real commands.
Stripe Webhook Signature Verification Failed: A Debugging Guide
Diagnose and fix Stripe webhook signature verification failures. Covers common causes like clock drift, wrong signing secret, and raw body mismatches.
Firebase Security Rules Blocking Requests: Debugging Guide
A practical guide to debugging Firebase Security Rules that unexpectedly deny requests. Covers simulator pitfalls, missing auth tokens, and rule ordering issues.
Supabase RLS Blocking Query: How to Diagnose and Fix Row-Level Security Issues
A practical guide to debugging queries blocked by Supabase Row-Level Security, covering common pitfalls, diagnostics, and concrete fixes.
Long-form thinking on debugging habits, observability, and the systems around the bug.