Lot of software engineers don't understand basic networking
13 points
3 hours ago
| 5 comments
| oneuptime.com
| HN
9rx
20 minutes ago
[-]
Stands to reason. It is all abstracted away.

I used to understand networking in decent detail, but now many years later I've forgotten most of it.

reply
wiz21c
2 hours ago
[-]
Lots of network engineer don't understand the usefulness of a stack trace.

IOW: when my network fails "No route to host", I want to know who failed and why. Not just "hey, start the route tool on your production sever which you don't have access to, to get to know who slipped"

reply
freedomben
13 minutes ago
[-]
You're kind of proving the articles point here. The networking stack doesn't surface that information to your code, because it doesn't have that information. To get that information, The various tools do a lot of extra things that don't typically happen on a normal network connection. This is kind of the like complaining that your typical release build stack trace doesn't also include profiling and debug information in it.
reply
9rx
1 minute ago
[-]
You're still thinking of software engineers, it seems. They have to jump through hoops to get that information.

The parent is talking about network engineers. In other words, he is saying the the network should have been designed at the ground level to naturally provide that information without the need to do a lot of extra things.

reply
mikestew
16 minutes ago
[-]
Kind of a crap article that seems to be a thrown-together reading list. The subtitle promises more than TFA delivers.
reply
compressedgas
3 hours ago
[-]
I was expecting examples. There were none.
reply
webdev1234568
1 hour ago
[-]
Just another AI blog post.. moving on.
reply