Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Beej's Guide to Network Programming

beej.us

Post reply on HN
Print view View original

71–80 of 91 posts

Re: Beej's Guide to Network Programming

#71

Post by InitialLastName »

ly3xqhl8g9 wrote: post #62
mu53 wrote: post #29

Earlier quoted context omitted.

I love this level of honesty. It is true, but people never say it

Here's a product (Gmail/Outlook add-on or so): have your own LLM trained over your public texts (articles, books, blog entries, READMEs, Hacker News comments, and so on), mark the emails you can't respond to with the "GPT" label which puts the mail in a queue and if you don't remove the label in 7 days or so, it sends a response with a polite intro "I didn't have the time to get to your email, but here's what I might…

Yep, absolutely no career-terminating downside opportunity in this one.

Re: Beej's Guide to Network Programming

#72

Post by Jorengarenar »

lannisterstark wrote: post #48
keyle wrote: post #23

There is also a C guide [1] which has a pretty interesting email policy... I’m generally available to help out with email questions so feel free to write in, but I can’t guarantee a response. I lead a pretty busy life and there are times when I just can’t answer a question you have. When that’s the case, I usually just delete the message. It’s nothing personal; I just won’t ever have the time to give the detailed ans…

Why not like ...just leave the message alone lol? We don't have 64 Kilobytes of limited memory on our email servers anymore.

Liking to have clean and empty inbox isn't related to limited memory

Re: Beej's Guide to Network Programming

#73

Post by tonightstoast »

sph wrote: post #60
vajrabum wrote: post #13

All Beej's guides are fantastic, but if you're interested in Network programming you could do way worse than follow this up with his guide to network concepts. https://beej.us/guide/bgnet0/ If you search Algolia for Beej you'll see his material has been on hacker news numerous times.

Anyone knows of a well-rounded guide that explains the structure of the Internet at large? I know everything listed in the one you linked, but I have a nebulous idea of how anything works after my packet exits my gateway. So, BGP, autonomous systems, peering agreements and other site-to-site routing protocols that keep the entire Internet infrastructure ticking along.

https://learn.cantrill.io/p/tech-fundamentals

I found Cantrill’s course pretty solid. It is free and you can just skip to DNS & DNSSEC.

Re: Beej's Guide to Network Programming

#74

Post by JustSomeNobody »

kqr wrote: post #38

Open question: in what fields are you working where you really need to work with actual sockets? Most of the network programming I do fall into one of two categories: 1. A library exists to abstract over the bytes-into-sockets layer, meaning I don't need to deal with it; or 2. A library probably exists to abstract over the bytes-into-sockets layer, but I've chosen to ignore it either because I'm truly ignorant of it,…

I implement protocols to communicate with various hardware (RFID, LiDAR, etc). Most of these communicate over sockets. Some still use serial. I have a library I wrote of socket routines that I use, so it's not like I re-implement that every time, though. And for this, I'd really rather use my library than a 3rd party in case I have to dig in and see what's going on.

Re: Beej's Guide to Network Programming

#75

Post by JustSomeNobody »

forrestthewoods wrote: post #39
kqr wrote: post #38

Open question: in what fields are you working where you really need to work with actual sockets? Most of the network programming I do fall into one of two categories: 1. A library exists to abstract over the bytes-into-sockets layer, meaning I don't need to deal with it; or 2. A library probably exists to abstract over the bytes-into-sockets layer, but I've chosen to ignore it either because I'm truly ignorant of it,…

There is a whole universe of programming that exists outside of webdev. Firmware, video games, high performance systems, etc.

This. I think HN leans very heavy on webdev and somehow forgets that the entire rest of the planet runs on software also.

Re: Beej's Guide to Network Programming

#76

Post by ly3xqhl8g9 »

InitialLastName wrote: post #71
ly3xqhl8g9 wrote: post #62

Earlier quoted context omitted.

Here's a product (Gmail/Outlook add-on or so): have your own LLM trained over your public texts (articles, books, blog entries, READMEs, Hacker News comments, and so on), mark the emails you can't respond to with the "GPT" label which puts the mail in a queue and if you don't remove the label in 7 days or so, it sends a response with a polite intro "I didn't have the time to get to your email, but here's what I might…

Yep, absolutely no career-terminating downside opportunity in this one.

Good thing that with the coming devastating job purges due to statistical learning such "careers" based around bullshit jobs [1] where some words in a generated email can be "career-terminating" will be forever gone.

[1] https://en.wikipedia.org/wiki/Bullshit_Jobs

Re: Beej's Guide to Network Programming

#77

Post by sph »

tonightstoast wrote: post #73
sph wrote: post #60

Earlier quoted context omitted.

Anyone knows of a well-rounded guide that explains the structure of the Internet at large? I know everything listed in the one you linked, but I have a nebulous idea of how anything works after my packet exits my gateway. So, BGP, autonomous systems, peering agreements and other site-to-site routing protocols that keep the entire Internet infrastructure ticking along.

https://learn.cantrill.io/p/tech-fundamentals I found Cantrill’s course pretty solid. It is free and you can just skip to DNS & DNSSEC.

Oh, that's exactly what I was looking for. Thanks!

Re: Beej's Guide to Network Programming

#78

Post by InitialLastName »

ly3xqhl8g9 wrote: post #76
InitialLastName wrote: post #71

Earlier quoted context omitted.

Yep, absolutely no career-terminating downside opportunity in this one.

Good thing that with the coming devastating job purges due to statistical learning such "careers" based around bullshit jobs [1] where some words in a generated email can be "career-terminating" will be forever gone. [1] https://en.wikipedia.org/wiki/Bullshit_Jobs

I think I'd argue that the people whose emails can be sufficiently answered with an LLM are the ones whose jobs are first on the chopping block, so the product has a self-destructing user base.

Re: Beej's Guide to Network Programming

#79

Post by ly3xqhl8g9 »

InitialLastName wrote: post #78
ly3xqhl8g9 wrote: post #76

Earlier quoted context omitted.

Good thing that with the coming devastating job purges due to statistical learning such "careers" based around bullshit jobs [1] where some words in a generated email can be "career-terminating" will be forever gone. [1] https://en.wikipedia.org/wiki/Bullshit_Jobs

I think I'd argue that the people whose emails can be sufficiently answered with an LLM are the ones whose jobs are first on the chopping block, so the product has a self-destructing user base.

Not necessarily. When I was writing the initial comment I wasn't even thinking about job-related mails, but at someone like Sean Carroll who does a regular Ask me Anything [1] where lots of questions are skipped for lack of time, or in general academics who receive plenty of emails about articles and various field-related questions.

[1] at the beginning of each month, May 2023 https://www.youtube.com/watch?v=h_GD4E27Bt8

Re: Beej's Guide to Network Programming

#80

Post by bachmeier »

keyle wrote: post #23

There is also a C guide [1] which has a pretty interesting email policy... I’m generally available to help out with email questions so feel free to write in, but I can’t guarantee a response. I lead a pretty busy life and there are times when I just can’t answer a question you have. When that’s the case, I usually just delete the message. It’s nothing personal; I just won’t ever have the time to give the detailed ans…

I can speak from experience that posting that type of material will generate some interesting email inquiries. I used to get email messages with a 4000-line program, multiple datasets, and "My program doesn't work. Can you tell me what the error is?" The awkwardness of deleting the message is less than the awkwardness of refusing what someone else views as a 30-second request.
Post reply on HN