Post B6tr7kmfy5p0xUqiC8 by coolboymew@shitposter.world
(DIR) More posts by coolboymew@shitposter.world
(DIR) Post #B6tr0l5SRYyDs4IaDQ by Lars@shitposter.world
2 likes, 0 repeats
Previous role was like a weird NOC+Customer Support position with an ever-expanding job scope and customer-facing. Everyone was always polite and whatnot in the 40+ persistent chats but talked shit in private chats.New role is in a true NOC working closely with the network engineers. So far only been added to 1 group chat for it and everyone's vulgar, cussing out their laptops, network devices, etc.
(DIR) Post #B6tr7kmfy5p0xUqiC8 by coolboymew@shitposter.world
0 likes, 0 repeats
@Lars ISP? From what I have seen of small ass ISPs, it's a shitshow of a job
(DIR) Post #B6tr9Hgb7oPJI9jhPU by Lars@shitposter.world
1 likes, 0 repeats
@coolboymew Mastercard
(DIR) Post #B6trAzgwzxfm3wiTg0 by coolboymew@shitposter.world
0 likes, 0 repeats
@Lars oh man
(DIR) Post #B6trZwNyQYh334jfNI by Lars@shitposter.world
1 likes, 0 repeats
@coolboymew Previous role mostly worked with banks + ISPs + hardware vendors. Doing basic tasks like troubleshootign network outages, processing RMA's, informing banks they're taking impact, etc. For deeper network issues or changes, they'd escalate to our engineers. However our engineers take on a lot of work and are on-call on weekends, etc. So they came out with a new role to be the in-between; a true NOC to take the troubleshooting escalations, etc. with 24/7 coverage. That's what I just joined.
(DIR) Post #B6tsIWxJp1HpD6WvCq by mangeurdenuage@shitposter.world
2 likes, 0 repeats
@Lars @coolboymew >However our engineers take on a lot of work and are on-call on weekends, etc>So they came out with a new role to be the in-between; a true NOC to take the troubleshooting escalations, etc. with 24/7 coverage.Sounds like they have shit tons of technical debt and they don't have the manpower to manage it so they're just adding buffers thinking it will give them time to sort it up.
(DIR) Post #B6tt1SjqLftrA5eUzo by Lars@shitposter.world
1 likes, 0 repeats
@mangeurdenuage @coolboymew This is pretty much exactly what's happening in my previous department. They added really poor automations that are drastically increasing the workload for a much smaller work force. They plan to have the automations do more than just open tickets, for it to be able to engage providers, close tickets, etc. but for now it only opens tickets for every alert, doesn't matter if it was jsut a quick BGP flap or if there was a change ticket open for it or anything. It even opens multiple tickets if it's like a circuit between two of our own devices, 1 ticket for each device for the same outage. Or even 15 tickets if it's a regional circuit provider outage; same outage but different devices at different sites and the automation doesn't know any better. Then ITSM doesn't want them cancelling tickets and is always adding more and more requirements to close them.I can see if they can perfect the automations that it could completely replace the network side of my old department then my new department would basically take over what it can't do.