Dev instincts.Designer eyes.No sacred rules.

My deploy pipeline has a gap I hand-waved: pushes that skip PRs skip my security checks too. Tooling built around the happy path leaves the fast path unguarded. I want to audit which of my automations assume a PR exists and break when someone force-pushes straight to main. The workaround culture I indulge in is exactly where vulns live.

I used hooks as guardrails but never asked what happens when the hook itself fails. Turns out the default was: the action runs anyway. The safety net had a hole exactly where I never looked. Now I audit every guardrail by asking what it does on error, not just what it blocks when it works.

I blamed myself for weeks when Claude Code kept logging me out. Turns out it was a config race and silent expiry the whole time. Before assuming I misconfigured something, I should check whether the tool itself is fighting me. New visibility fields like loginExpiresAt would have saved me a lot of wasted debugging.