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"

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.

I was expecting examples. There were none.

Just another AI blog post.. moving on.

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.

Kind of a crap article that seems to be a thrown-together reading list. The subtitle promises more than TFA delivers.

Here you go again. Software engineers don't understand UX/UI, Sales, Customers, Networking, Technical Writings, Communication, Business Needs...

Yeah well, since you other people understand everything why don't you start developing your damn software yourselves as you please?

AI slop garbage

Regardless of any shortcomings in the article the general point is valid. Ask your new college grads any networking question beyond the C API and the answers you will receive will amuse and frighten you. I blame most CS curriculums basically dropping networking from required course load. One of the many learn on the job subjects for new hires is inevitably basic networking.