Streams: a new general purpose data structure in Redis
One thing I like about this post is the story of how the feature came to be: Someone who understood redis very well, thinking about the problem over literally years, eventually resulting in a more targetted and goal-driven thinking, and even that "specification remained just a specification for months, at the point that after some time I rewrote it almost from scratch in order to upgrade it with many hints that I accumulated talking with people about this upcoming addition to Redis."I've been thinking about this sort of thing for a while, wanting to maybe call it "slow code" (like "slow food").  This is how actual quality software that will stand the test of time gets designed and made, _slowly_, _carefully_, _intentionally_, with thought and discussion and feedback and reconsideration. And always based on understanding the domain and the existing software you are building upon.   Not jumping from problem to a PR to a merge. (And _usually_ by one person, sometimes a couple/several working together,  _rarely_ by committee).