3 ms·

I don't know how old you are but my career now exceeds two decades. I definitely see this more now but that's because I institute it. Earlier in my career, we

I don't know how old you are but my career now exceeds two decades. I definitely see this more now but that's because I institute it. Earlier in my career, we failed at incident management and at ownership. We now share the burden of on-call not just with the operators (sysadmins or old) but also with the people who wrote the code. We've spent a lot of time building better models based on proven methods, quite a few come from work done in high intensity roles paid by tax dollars: risk analysis, disaster recovery, firefighting, command and control, incident management, war games, red teams.

dvtrn 5y ago
You've got a couple of years on me, I've been in the game a little over 13 years now. I support the notion there's a strong difference between lingo that's properly applied to the situation and lingo that is recklessly applied because it "sounds cool". The examples you gave seem to be fair game for the work being done-in the interest of brief, specific language; the examples I gave in another comment though ("flanking","breaching") however are just grating and...weird to use in a work environment. Your point is nevertheless well met.