I don't really understand comments like this on HN. I've derived a lot of value through the years from thoughtful questions asked to dig further into an article but I've never understood why somebody would assert "I don't even know what X is." Search engines exist, yes?
But it's not an "article". It's a blog post. An informal post, written informally, for an obviously technical audience.
I very, very rarely explain what "AWS" is when I'm casually writing about cloud stuff. It's table stakes. You should know, or you aren't gonna appreciate reading it anyway.
Logged in just to upvote your comments. This is a place of intellectual curiosity, and I don’t understand those who expect knowledge to be spoon fed to them. If you don’t know a term, search engine it and work your way down the stack.
You might find yourself pleasantly surprised you’re providing an NTP server in the NTP global DNS pool.
When I need to google a term, I highlight it, and then press ⌘C, ⌘T, ⌘V, enter. (Copy the search term, open a new tab, paste into url/search bar, search term)
I've gotten quite fast at the keyboard sequence; it takes maybe one second total. I imagine I could make this process even faster with a plugin, But I see no need.
I would like to think that most Windows machines would let you be similarly performant by default. But if not, that's further evidence in my book that Windows just sucks...
I will note that some acronyms can be annoyingly un-googlable, as the same one stands for a wide variety of different terms. This problem does not apply to ntp, however, which comes up right away.
My point was that the OP can't guess their readers' level of knowledge, and it would be impossible for them to cater to all levels (as my attempt to explain searching... failed to show :-/) If readers don't know what NTP is, they should be able to either ignore the blog post or find the missing bits of their knowledge by themselves.
I agree with you but if you take the time to just maybe write out an acronym once its much easier for us who aren't quite there yet technically to understand the context instead of having to search for 4-5 terms. This gives us a chance to enjoy the write up and gives it maybe a broader audience.
This is a technical person blogging for a technical audience. If you are not tall enough to ride this ride and aren't interested in growing, maybe find another ride.
If this were a project blog post explaining their latest features, I'd agree with you. If the point is outreach, then yes, they should make it accessible. But he's telling a story. A story that requires a relatively deep understanding of the history and practice of operating internet services. Him writing "NTP (Network Time Protocol)" will not make the story much clearer. And if he explains the whole background, then it's no longer a story, it's a general-audience essay. That's a lot of work for you to expect from somebody that you aren't paying.
You don't actually need to know what NTP is to enjoy this story. I knew I had heard of NTP but had forgotten about it. But it ends in P so it must be some protocol or other, right? Just create a variable in your mind called $protocol and keep reading. It could just as easily be Zuqwatny Protocol at that point for all I care.
That said, I went and looked it up after. Because that's what you do.