Support as a Craft

For fourteen years, when the software broke, the phone that rang was mine. That teaches things no course can.

The technical half

Real diagnosis runs: reproduce first; read the logs before touching anything; query the database to see what the system believes; find the divergence between belief and reality; fix the cause, not the symptom; then confirm with the user and write it down. I've done this across desktop clients, web applications, sync pipelines, and integrations — systems where a wrong "fix" corrupts business data. Speed matters, but sequence matters more.

The human half

The person calling is not interested in your architecture — they're behind on their day and someone is queuing at their desk. The craft is: lower the temperature, translate the problem into their language, give an honest status (including "I don't know yet — here's when I'll update you"), and never let a ticket go silent. I learned to be measured on response time, resolution quality, and whether the user hangs up feeling helped — and I'd welcome being measured on exactly those things again.

Escalation, when you are the escalation

Running support with no tier above you builds a specific muscle: complete ownership. Nothing could be someone else's problem. Inside a team, that muscle turns into the colleague who takes the ugly ticket, documents what everyone else worked around, and closes loops others leave open.