To be fair, networking is hellish for a variety of reasons.
I took 1 networking (IT midtier elective) class in college as an elective and even though it was super basic in reality, it was very annoying in that nothing felt automatic, even though 99.9% of everything felt like there should be. Usually if that's the case I'd learn/be told there was some automatic stuff (Take a compiler class -> learn of YACC and they you never write your own compiler). But networking? Not really as far as I've ever seen. Sure there's some stuff, but it always seems to come around to "This works except when you need to know the exact details of https once a year".
Ironically I'm on the interconnect team at my current work. Even though we rely on shit, we avoid touching 90% of the stuff we own that actually does the connecting, and avoid setting up crap because its a mess.
To be fair, networking is hellish for a variety of reasons.
That has nothing to do with it. My company maintains network software for server instances which maintain thousands of simultaneous user connections continuously (and loads of continuous bandwidth). Simple "networking is tough" is not an answer for why it apparently costs this company half-a-mill a month to maintain 32 active connections. There is no good answer to that. It's just poor management/bureaucracy, including their choice of infrastructure. And labor, obviously.
How are there so many problems that can be fixed by figuring out how to log into a router and then telling it "1.1.1.1" instead of "0.0.0.0."
Like my fucking graphics card doesn't shut off periodically and go "oh damn should I try ones? Or maybe twos? Pleas tell me a number so I can turn back on again
To be fair, networking is hellish for a variety of reasons.
I took 1 networking (IT midtier elective) class in college as an elective and even though it was super basic in reality, it was very annoying in that nothing felt automatic, even though 99.9% of everything felt like there should be. Usually if that's the case I'd learn/be told there was some automatic stuff (Take a compiler class -> learn of YACC and they you never write your own compiler). But networking? Not really as far as I've ever seen. Sure there's some stuff, but it always seems to come around to "This works except when you need to know the exact details of https once a year".
Ironically I'm on the interconnect team at my current work. Even though we rely on shit, we avoid touching 90% of the stuff we own that actually does the connecting, and avoid setting up crap because its a mess.
That has nothing to do with it. My company maintains network software for server instances which maintain thousands of simultaneous user connections continuously (and loads of continuous bandwidth). Simple "networking is tough" is not an answer for why it apparently costs this company half-a-mill a month to maintain 32 active connections. There is no good answer to that. It's just poor management/bureaucracy, including their choice of infrastructure. And labor, obviously.
Yeah networking is fucking insane, like
How are there so many problems that can be fixed by figuring out how to log into a router and then telling it "1.1.1.1" instead of "0.0.0.0."
Like my fucking graphics card doesn't shut off periodically and go "oh damn should I try ones? Or maybe twos? Pleas tell me a number so I can turn back on again