3 ms·
Relentless customer service is never going to screw you over in my experience... It pains me that we have to constantly play these games of abstraction between
by bob1029 5y ago
Relentless customer service is never going to screw you over in my experience... It pains me that we have to constantly play these games of abstraction between engineer and customer. You are presumably working a job which involves some business and some customer. It is not a fucking daycare. If any of my customers are pissed about their experience, I want to be on the phone with them as soon as humanly possible and I want to hear it myself. Yes, it is a dreadful experience to get bitched at, but it also sharpens your focus like you wouldn't believe when you can't just throw a problem to the guy behind you.
By all means, put the support/enhancement requests through a separate channel+buffer so everyone can actually get work done during the day. But, at no point should an engineer ever be allowed to feel like they don't have to answer to some customer. If you are terrified a junior dev is going to say a naughty phrase to a VIP, then invent an internal customer for them to answer to, and diligently proxy the end customer's sentiment for the engineer's benefit.
- ethbr0 5y agoI think of this is terms of empathy: every engineer should be able to provide a quick and accurate answer to "What do our customers want? And how do they use our product?" I'm not talking esoterica, but at least a first approximation.
- yaknh 5y agoWhy? Like we all are customers as well as an employee.
- ativzzz 5y agoBecause we as engineers create software for our customers, and if you don't understand who your customers are how can you create software that actually suits their needs? Very rarely are we our own customers
- fragmede 5y agoI would argue that SREs are consistently our own customers in a way unique to SRE.
- ethbr0 5y agoIronic, as measurability came up in another comment thread I'm in. I'd say from a technical perspective SREs are, but there's a potential (depends on product) gap between their technical goals and user goals. e.g. What does "p95 latency is spiking" actually mean to the end user?