Hasan Yahya U.’s Post

This can be changed! 1% solving network issues. 20% implementing solutions that reduce mean-time-to-innocence. 10% proving that it is not a network issue. 30% improving the network quality. What will you do with the remaining 39%? I would be developing my skillset for the future (which is now!)

We don't make mistakes; if we did, it was by mistake.

We had seemingly the opposite problem for a while. We had to prove it was a network problem before they would take the time to look. We had no access to prove it was a networking issue so issues would continue sometimes for weeks. Eventually, my manager convinced them to give me read access to switches and firewalls so I could send screenshots of the Rule/ACL that was the problem and ask for a fix. Network tickets dropped by like 80% after that.

Statement is true only for engineers with network background only. Engineers with knowledge of networking, hardware and software are highly appreciated as they are capable to identify and solve the problem which in turn saves tons of money for the Customer

Truth is, in the effort of the 99% we get that 1% 😊

It's IMO not about tech problems, it's about dealing with people. I also know from experience, that I spend hours to prove (or rather convince the guy) that it's their typo in their yaml file, which generates the error not a misconfiguration in the system.

POV you are SysAdm : App and services up and running/listening. Check the firewall rules and routes. 😂

Ehh, in my experience.. It was always more like: Within that 1% possibility range when it's an actual network issue, explaining it actually is a network problem to network people AND providing a solution to their problem between their defacto copy paste denial emails.

I know many experts who are obsessed to move tickets into ‘CUSTOMER ACTION NEEDED’ bin.

Rahul Bormale periyasamy s Ravi Dhage Bhalchandra Dhebe Moin khan