Lot of software engineers don't understand basic networking
1–10 of 11 posts
Re: Lot of software engineers don't understand basic networking
#2I was expecting examples. There were none.
Re: Lot of software engineers don't understand basic networking
#3Lots 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"
Re: Lot of software engineers don't understand basic networking
#4Just another AI blog post.. moving on.
Re: Lot of software engineers don't understand basic networking
#5Stands 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.
Re: Lot of software engineers don't understand basic networking
#6Kind of a crap article that seems to be a thrown-together reading list. The subtitle promises more than TFA delivers.
Re: Lot of software engineers don't understand basic networking
#7Lots 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.
Re: Lot of software engineers don't understand basic networking
#8Lots 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…
[deleted]
Re: Lot of software engineers don't understand basic networking
#9Here 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?
Re: Lot of software engineers don't understand basic networking
#10AI slop garbage