You are viewing a single comment's thread.

view the rest of the comments →

0
1

[–] ditch-digger [S] 0 points 1 point (+1|-0) ago 

I think you misread that, usually L1 won't bother reading, kick it of to L2 where I'll let it sit till SLA has almost expired (if the network isn't actually down) then handle it. I think I've only had to send 1 of to the data center. This was really more of an FU to users. Even if you infrastructure cunts keep sending updates to my legacy app. Ran fine a decade ago, now I gotta retest everything because we're changing the OS.

0
0

[–] 1moar ago 

Nah, I get it. I just hold a special hatred for app owners, 3rd party devs and those that ALWAYS point to the network. We update the ios on routers or switches, that's it as far as updates outside of major infrastructure changes.

99% of the time, it's not network. I get ya though, but network hates this shit. Every week, same people, same conversation.

We're not without fault, but holy shit it grinds my gears.

0
1

[–] ditch-digger [S] 0 points 1 point (+1|-0) ago 

3rd party devs can eat a bag of baby dicks. Actually my offshore devs can join in. I reverse engineer the code, get down to the root cause, and have to solve the fucking issue 100% of the time. My colleges are those fucking roaches you hate, as is my boss. Actually, the only thing I usually can count on is the network (except one time a ferret ate through the fiber optics at the data center and took down the company, awesome ferret!)