upvote
You're right.

In general when selecting articles we assume that the reader is an expert in some field(s), but not necessarily in the field covered by this article. As such, things which are simple for an expert in the specific domain, can still be surprisingly to learn for folks who aren't experts in that domain.

What I'm saying is, that we don't try to be a cutting edge scientific journal — rather than that, we publish even the smallest trick that we decide someone may not know about and find it fun/interesting to learn.

The consequence of that is that, yeah, some article have a bit clickbaity titles for some of the readers.

On the flip side, as we know from meme-t-shirts, there are only 2 things hard in computer science, and naming is first on the list ;)

P.S. Sounds like you should write some cool article btw :)

reply
For what it's worth, I am only a mid-tier nerd and after reading this issue, I feel like I am your target audience. Nothing deep or overly-detailed, just lots of jumping-off points for me to learn more. Thanks!
reply
I noticed that as well. Also misleading titles like “Eliminating Serialization Cost using B-trees” where the cost savings are actually for deserialization (from a custom format), and neither the self-balancing nature of B-trees isn’t actually relevant, as no insertion/deletion of nodes occurs in the (de)serialization scenario, so a single tree level is sufficient. It’s a stretch to refer to it as a B-tree.
reply