Skip to content

Instantly share code, notes, and snippets.

@simonholm
Created November 12, 2025 07:22
Show Gist options
  • Select an option

  • Save simonholm/e335f4093e77f1d7b352cf3b525db39f to your computer and use it in GitHub Desktop.

Select an option

Save simonholm/e335f4093e77f1d7b352cf3b525db39f to your computer and use it in GitHub Desktop.
Tech issue reporting guide

Quick Tech Issue Reporting Guide

The Problem

Vague reports like "status issues" or "operational disturbance" require multiple clarification rounds.

Solution Pattern

Subject + Specific Problem

Examples

Service Status Queries

  • ? "status issues, like yesterday"
  • ? "Is Claude.ai down?"
  • ? "Claude.ai service status?"
  • ? "Anthropic outage check?"

System Issues

  • ? "having problems"
  • ? "MCP servers - not responding in Desktop"
  • ? "WSL - disk full errors"
  • ? "Backup script - failing on line 47"

Standard Tech Terminology

Service Availability

  • Outage - complete service failure
  • Downtime - period when service unavailable
  • Service disruption - partial failures or degraded performance
  • Degraded performance - slow but working
  • Incident - official term on status pages

Avoid

  • "Operational disturbance" (uncommon, sounds corporate)
  • Ambiguous subjects that could mean multiple systems

Quick Reference: Status Checks


Created: 2025-11-12

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment