found in my archives
You must log in or # to comment.
SRE:
- Receives a slack message that lighbulb is broken
- Realizes that they never got an alert when the light went out
- Fixes their monitoring thresholds
- Routes all broken lightbulb alerts to a slack channel nobody reads
Full stack developer:
The lightbulb is broken. Deploys a lightweight fix that involves 17 metric tons of chandeliers, stadium floodlights, sconces, and the necessary infrastructure to operate the street lights for a city of 500.000. His solution delivers a solid 100 lm of light using only 175 MW of power.
I’d say I feel seen, but it’s really dark in here.
Who said that?
[clicks light switch off and on repeatedly]
Welp, I guess we’re closed for the week.
That’s the end user.
no no, the end user will somehow find the exact position in which the switch starts arcing and then they’ll work by the light of the fire in their walls.
Support would be like
User reports lightbulb is broken. Tries to talk user through troubleshooting. Problem resolved by turning on light.
I wish users would report their problem istead of what they think is the solution. It’s more like: Hey support, I need a floorplan of the building containing positions of all electrical wiring. High priority, department is at a complete stop rn!
I wish users would report their problem istead of what they think is the solution.
And when they do report the problem, they should report the actual problem they had and not what they think the problem is.
So instead of eg. “my computer’s been hacked!”, it’s actually “I saw a scary error dialog I didn’t understand”
That sounds roughly related. I see ones like: excel file broken!!! Actual issue: it’s dark so the computer screen is too bright and when they put sunglasses on due to the brightness, they can’t read the numbers. Solution is to turn the lights on.
