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
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
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.
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
Those last couple of steps actually involve a shotgun and condolences to the devs family. Take no shit.
My 14 yo would be stoked. He’s right into networking tech.
Doesn’t really care about Nintendo.
I wish I was into networking at 14, I'd be making more money now. That's a great start he's got
We were all into networking when I was young. Had to make Lan parties and UT servers work somehow.
Everyone still ended up working factory / distribution jobs lol.
Me too, but it didn’t really exist when I was 14.
Not everything needs to be about making money, just reminding you that that's pretty vile.
Having money isn't everything. Not having money is.
Lol
Having the means to support yourself and a family with a decent standard of living isn't everything, you're right. It's a lot tho.
The spirit of Christmas, everyone.
theres a chance that thing cost more than a Nintendo Switch
Pretty damn good chance tbh. I know I can’t afford that thing.
Hmm...that one's probably around 150 gently used.
I would be pissed if I got a 10/100 catalyst switch too.
It's not Santa's fault, he's thousands of years old so he probably had his IT stack built out ages ago and never bothered to consider upgrades so he just assumed that 10/100 was still state of the art!
He's probably using cloud services, makes sense, why build out infra he'll have to manage 365 when he basically needs it 2 months a year?
Alright now hook that shit up to the router, don't forget to create a LAG or you'll create a broadcast storm, and I'm in a WoW raid in ten minutes so make it fast.
Are you just throwing networking terms together? How does a LAG prevent a switching loop?
LAG are aggregated interfaces and they can indeed be used to prevent (some) layer 2 loops. LAG as in Link Aggregation Group)
Using 2 non-LAG interfaces between the same 2 devices creates a loop.
In the case of a loop, if you're running spanning tree, one of these interface will be blocking instead of forwarding, preventing the loop, but also percentile the use of this interface until the topology changes (ie: the current one goes down).
If you're not running spanning tree for some reason, then both interface will chug along, oblivious to the fact that there's a loop and broadcast packets will indeed keep being flooded on one and received on the other, again flooded, etc. creating a broadcast storm and impacting performance of the whole layer 2 domain and possibly even crashing devices.
A LAG more or less means the interfaces in the group behave as one big (aggregated) interface.
LAG also means you can push traffic on both interfaces for more bandwidth.
Source: Network engineer Internet plumber
It doesn't.
The assumption is that they're creating a high bandwidth trunk interface to the L3 switch/router, so if they forget to create an aggregate it'll be two independent interfaces and will down the network (or a port will auto down itself with STP, MSTP, etc. but that's not as funny)
A router of industrial scale which i see at work has its ports to be l3 ports by default. They don't down the network as the router rejects config where two ports are given the same subnet.. at least the ones i operate at work.
That's true, the default for layer 3 switches is to have its port set as routable.
The original joke really kinda falls flat with modern tech, but it's still funny to think about handing a switch to someone with zero knowledge and then watch as they accidentally lock up the environment.
Better than a light switch.
What about a heavy switch?
So that's why Nintendo uploaded that video explaining the Switch after 7 years selling it.
Lol I would've been pumped if I got this as a kid
First out-loud laugh of the day. Love it.
Please don't show us what a Wii would look like.
Don't kinkshame!
That is such a 90s couch. :o
i got a cat toy one year instead of a computer mouse. my mom thought it was hilarious.
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
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
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.
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
Those last couple of steps actually involve a shotgun and condolences to the devs family. Take no shit.
My 14 yo would be stoked. He’s right into networking tech. Doesn’t really care about Nintendo.
I wish I was into networking at 14, I'd be making more money now. That's a great start he's got
We were all into networking when I was young. Had to make Lan parties and UT servers work somehow.
Everyone still ended up working factory / distribution jobs lol.
Me too, but it didn’t really exist when I was 14.
Not everything needs to be about making money, just reminding you that that's pretty vile.
Having money isn't everything. Not having money is.
Lol
Having the means to support yourself and a family with a decent standard of living isn't everything, you're right. It's a lot tho.
The spirit of Christmas, everyone.
theres a chance that thing cost more than a Nintendo Switch
Pretty damn good chance tbh. I know I can’t afford that thing.
Hmm...that one's probably around 150 gently used.
I would be pissed if I got a 10/100 catalyst switch too.
It's not Santa's fault, he's thousands of years old so he probably had his IT stack built out ages ago and never bothered to consider upgrades so he just assumed that 10/100 was still state of the art!
He's probably using cloud services, makes sense, why build out infra he'll have to manage 365 when he basically needs it 2 months a year?
Wonder if he uses Amazon Glacier
Anyone got any idea on data retention requirements for Lapland?
Aha, that's why I never get what I want for Christmas: classic ASP.
You might end up with an asp instead!
Only 2x SFP cages? I'd be pissed too. And I bet they're only 1gbps
looks like an early cisco 3400
10/100, so youre prolly on the money there for sale!
"there"
what networking term will they use for the next one? ndp?
DNS: Double Nintendo Switch
Guy’s thoughts: “I asked for a switch, but I got a router!”
Alright now hook that shit up to the router, don't forget to create a LAG or you'll create a broadcast storm, and I'm in a WoW raid in ten minutes so make it fast.
Are you just throwing networking terms together? How does a LAG prevent a switching loop?
LAG are aggregated interfaces and they can indeed be used to prevent (some) layer 2 loops. LAG as in Link Aggregation Group)
Using 2 non-LAG interfaces between the same 2 devices creates a loop.
In the case of a loop, if you're running spanning tree, one of these interface will be blocking instead of forwarding, preventing the loop, but also percentile the use of this interface until the topology changes (ie: the current one goes down).
If you're not running spanning tree for some reason, then both interface will chug along, oblivious to the fact that there's a loop and broadcast packets will indeed keep being flooded on one and received on the other, again flooded, etc. creating a broadcast storm and impacting performance of the whole layer 2 domain and possibly even crashing devices.
A LAG more or less means the interfaces in the group behave as one big (aggregated) interface.
LAG also means you can push traffic on both interfaces for more bandwidth.
Source:
Network engineerInternet plumberIt doesn't.
The assumption is that they're creating a high bandwidth trunk interface to the L3 switch/router, so if they forget to create an aggregate it'll be two independent interfaces and will down the network (or a port will auto down itself with STP, MSTP, etc. but that's not as funny)
A router of industrial scale which i see at work has its ports to be l3 ports by default. They don't down the network as the router rejects config where two ports are given the same subnet.. at least the ones i operate at work.
That's true, the default for layer 3 switches is to have its port set as routable.
The original joke really kinda falls flat with modern tech, but it's still funny to think about handing a switch to someone with zero knowledge and then watch as they accidentally lock up the environment.
Better than a light switch.
What about a heavy switch?
So that's why Nintendo uploaded that video explaining the Switch after 7 years selling it.
Lol I would've been pumped if I got this as a kid
First out-loud laugh of the day. Love it.
Please don't show us what a Wii would look like.
Don't kinkshame!
That is such a 90s couch. :o
i got a cat toy one year instead of a computer mouse. my mom thought it was hilarious.
I asked for a switch and all I got was a vers.