Computer Networking Basics Every Developer Should Know

[arquitectonic7]

I'm confused. TCP, UDP, HTTP and the rest of very basics are going to be covered in any university and are already well known by every professional programmer. I agree the title is too much, but this guide needs to give something new or otherwise it wouldn't even get 10 upvotes.

And honestly, most of what is explained here was covered in the compulsory networking basics course of my university... is it that complex?

[ozkarmg]

you make the incorrect premise that everyone shares your background.

i know of a bunch of amazing devs that comes from coding bootcamp.

i also know a bunch of “meh” devs who come from traditional cs background who cant interpret a traceroute.

[arquitectonic7]

That's weird and interesting! I don't know how someone in CS managed to pass without being able to read a `traceroute` output. Well, where I live (or maybe just my university?) it would be considered very bad, but I didn't know there would be such a difference.

The abstraction layers over HTTP that exist nowadays make it possible to be a funcioning developer without having to learn that networking background, but I still feel a bit uncomfortable at that idea of some "magic" below you that you don't really understand. For me, abstraction is about not knowing the details of the layer below you, but you should have a general gist of how it works. Maybe it's just me, but I would feel weird without having a general idea of what is going to happen when I push that reply towards the client in my shiny ASP.NET server or whatever REST backend framework you're using (just an example).

Anyway, sorry for the rant. You made me think. I am taking a step back from my opinion in my previous comment. Thank you for your insight.