A couple of days back, I was debating with one of my friend, about DEL vs UNLINK redis command. An interesting take; I come across that the majority of the people seemed to believe is "DEL is a blocking command. while UNLINK is non-blocking - so UNLINK is better". It's somewhat true - but it's not the full story.
So as an engineer, I unnecessarily dug into the Redis codebase to see the actual implementation.
wrote a blog for future me and my fellow strangers on the internet.
Meh...the phrase "deep dive" has been around forever, not sure what about that phrase specifically gives "AI generated" vibes? For me, I just read through those and focus on the content quality of the article - "verbal seasoning" doesn't phase me at all.
True, but I was commenting on the fact the commenter specifically called it a verb, while using it as a noun. I can't quote it now because the comment seems to have disappeared.
Ah right, missed that. The comment isn’t showing for you because you probably don’t have „show dead“ enabled in your profile settings. If you enable that, you’ll still see it.
It's very common, and increasingly common because of AI, since it was trained on a lot of meaningless business speak, but that doesn't mean it's not lazy and thoughtless, or particularly lazy and thoughtless now it's mindlessly pasted.
Have you ever been swimming? There’s absolutely such a thing as a surface dive which is what you do when you need to cover a great distance quickly in a shallow depth of water. It’s something every lifeguard who worked at a pool in america had to learn.
From an explanation analogy perspective people typically say something like “we’re just going to touch the surface”.
> A couple of my internet stranger friends and chatGPT says this number was chosen by redis developers post a massive benchmarking. The consideration was trade-off such as performance vs blocking, memory management and avoiding overhead.
Deep dive is a colloquialism in english, at least in the US.
We are going to see a lot of these about Redis since the source has so many comments. Basically re-stealing Salvatore's work again, unpriced asset.
17 comments
[ 3.2 ms ] story [ 47.0 ms ] threadSo as an engineer, I unnecessarily dug into the Redis codebase to see the actual implementation.
wrote a blog for future me and my fellow strangers on the internet.
> "Deep dive". When is a dive shallow? Isn't a dive implicitly deep?
https://news.ycombinator.com/item?id=42778951
Terms like this one, “alignment”, “low hanging fruit”, all not super accurate but established industry terms.
From an explanation analogy perspective people typically say something like “we’re just going to touch the surface”.
> A couple of my internet stranger friends and chatGPT says this number was chosen by redis developers post a massive benchmarking. The consideration was trade-off such as performance vs blocking, memory management and avoiding overhead.
Deep dive is a colloquialism in english, at least in the US.
We are going to see a lot of these about Redis since the source has so many comments. Basically re-stealing Salvatore's work again, unpriced asset.
"deep dive" has been around for quite some time https://trends.google.com/trends/explore?cat=5&date=all&q=%2...