"networking" in the social sense or in the administration/programming sense?
post
If it helps, I'm from the other side of networking and infra. You could swap the labels and make the meme accurate for me.
In the mid 1980s I learn the BASIC programming command GOTO and fell in love for a lifetime. If you look any anything I used to write in Ruby script or today in Python you'll see my love affair with "if" "elfi" and "else" continues. My universe is nested "if" statements all the way down.
Ahh, I found you, Toby Fox!
If you like if statements, you'll love the python case statements for pattern matching
Ohhh nice! I could see replacing dozens of nested if statements with dozens of nested case statements!

Please avoid nested if statements. Instead use early returns when possible.
It was fashionable at a time to avoid ifs and other imperative structures, but I tend to like them. Functional is nice and all but I like my code to be smart in the way it works, not in the way it's written. Nested ifs are readable, collapsible, and easy to make sense of at a glance, there's often nothing wrong with using them.
Same here! I can put together a half-descent network in just a few hours, but even programming simple stuff on microcontrollers is a major endeavor. And the documentation is usually terrible or nonexistent. And the tutorials are usually barely able to cover basic questions. At least in the space of networking, there’s enough context clues in the UI that I can piece together the solution I need.
In one college class we had to reimplement TCP in our own code on top of real UDP sockets. That was a fun class.
Fun, sarcasm?
The problem with networking is debugging it. The worst is debugging iptables and nftables. Figuring out which chain they are going to is a massive hassle. How come we don't have any graphical tools whatsoever for this work?
There's nothing to debug, it's fucking DNS again, you know it is.
I was like this 5 years ago. Networking a lot is still effort for me, but it is just another learnable skill, and it has lots of benefits (depending on your aims, I guess)
Edit: hah, just realised this is about connecting computers, not about talking to people...
Only wizards can configure iptables for ipv4 and ipv6 port forwarding. Only wizards.
And my boss shattering all with mean comments. Not letting me explain my code but still tearing it all down, removing all security features like checking for directory existing, connection is open aso. and then saying im not qualified for the job! Good thing i got already laid off. Bad that i'll still have to spend 3 months at this company
I'm so sorry about your job. :(
Do you mean that you were trying to write network conscious/safe code and your boss disagreed and laid you off for that reason?
tcpdump looks scary but is super neat and helpful, learn it if you haven't ;)
Still doesn't help with things like understanding routing and subnet masks and frame sizes and jfc how does any of this work
I've enabled all the relevant permissions. I've disabled firewall protection. I've enabled file sharing on both sides. I've checked for connectivity to the other machine from the command line...
Why is my shared folder still not accessible!??!
That's why I decided to build my first online multi-player game as an offline single-player game, and just figure out how to add the networking stuff when everything else is done- an architectural choice I definitely won't come to regret later...
My confidence in disk management and partition tables is made of horse hair, single strand.
I may actually be the other way around. I'm probably better at networking than programming? Not sure, I love them both but do neither professionally.
I've been trying to remotely connect to a relational database of medical data. I've been smashing my head against a keyboard for days trying to get my fucking code to work. I can't even connect to their db on their Jupyter Spark cluster
Ooh medical data, bet there is some security involved that "gets in the way".
top 50 comments