After setting up my own network, and trying to (kinda sorta) do it the right way (multiple SSIDs, vlan segregation, restrictive firewalls for iot, VPN to a VPS, etc.) — I have so much respect for network engineers. First month with my new router, felt like I “broke the Internet” every other day.
Or he could go it operations where every day is “a bad day to stop sniffing glue” because you are the only thing keeping the house of cards up while dev and network squabble over who’s foot cannon broke shit this time.
As a developer who knows enough about networking and servers to know when I’m out of my depth, I’m sorry for my colleague. If it’s any consolation we all think they are an idiot as well
Networking has to be the most confusing and tedious IT work I’ve ever done. I still don’t fully understand all the basics of security. But by far the worst part is that troubleshooting can’t be done like normal programming. Network troubleshooting takes forever, and all you get is a working network. Network work feels so dull even I have a hard time seeing my effort.
No kidding. There’s no debugger. You can’t just set a breakpoint and see what’s going on under the hood. It’s more like playing Russian roulette and hoping you don’t bring the whole network down.
It’s messing with the wiring while it’s still hot and there often isn’t a better way to do it.
Teach him to use it and send him down the path of one of the most frustrating career paths in existence…
Developer: Hey, I think the network is broken
Network Engineer: Okay, lemme check 30 seconds later nope, looking good, what’s up?
Developer: There’s a network issue, I ran this new code and lost everything.
NE: That’s… not really how the network works…
Dev: I’m a Developer, I know how the network works.
NE: Really…? Do you know how servers work?
Dev: Yes, of course. …
NE: Then why didn’t you look that your code crashed the VM you were using and you need to restart it…
Dev: …so it was a network issue?
NE: …
Dev: to other Devs Hey guys, don’t worry, it was a network issue, but I got them to do their job for once and fix it.
NE: resumes recreational liver destruction
After setting up my own network, and trying to (kinda sorta) do it the right way (multiple SSIDs, vlan segregation, restrictive firewalls for iot, VPN to a VPS, etc.) — I have so much respect for network engineers. First month with my new router, felt like I “broke the Internet” every other day.
As a developer, we’re not ALL like that
Or he could go it operations where every day is “a bad day to stop sniffing glue” because you are the only thing keeping the house of cards up while dev and network squabble over who’s foot cannon broke shit this time.
As a developer who knows enough about networking and servers to know when I’m out of my depth, I’m sorry for my colleague. If it’s any consolation we all think they are an idiot as well
Networking has to be the most confusing and tedious IT work I’ve ever done. I still don’t fully understand all the basics of security. But by far the worst part is that troubleshooting can’t be done like normal programming. Network troubleshooting takes forever, and all you get is a working network. Network work feels so dull even I have a hard time seeing my effort.
No kidding. There’s no debugger. You can’t just set a breakpoint and see what’s going on under the hood. It’s more like playing Russian roulette and hoping you don’t bring the whole network down.
It’s messing with the wiring while it’s still hot and there often isn’t a better way to do it.
It is too real man