Redis array: short story of a long development process
1–10 of 118 posts
Re: Redis array: short story of a long development process
#2Closely matches my own experiences with current SOTA AI. Extremely useful collaborator, far from being a replacement for human intelligence and creativity.
Re: Redis array: short story of a long development process
#3Is it possible to see the specification file you created and used for AI assisted development?
Very cool anyway! Can I expect a youtube video about this soon?
Re: Redis array: short story of a long development process
#4Closely matches my own experiences with current SOTA AI. Extremely useful collaborator, far from being a replacement for human intelligence and creativity.
There are projects that I develop mostly not looking at the code, but owning the concepts, algorithms and ideas asking questions and giving hints, and owning especially the product. But, not for Redis, not yet at least. When in the future this will be possible, server software, the way it is developed today, will be over. I bet there will be still projects and repositories, as accumulation of features, fixes and experiences will still be worth it, but the role of programmers will be very similar to what Linus did so far for the kernel. And for certain projects I'm developing, like the DeepSeek v4 inference engine, I'l already working like that.
Re: Redis array: short story of a long development process
#5Is it possible to see the specification file you created and used for AI assisted development? Very cool anyway! Can I expect a youtube video about this soon?
Yep I will release it, it is a bit out of sync at this point, but will do a pass of updating and will release it.
Re: Redis array: short story of a long development process
#6Closely matches my own experiences with current SOTA AI. Extremely useful collaborator, far from being a replacement for human intelligence and creativity.
I like to say, AI is the duck programming duck I always wanted
Re: Redis array: short story of a long development process
#7Closely matches my own experiences with current SOTA AI. Extremely useful collaborator, far from being a replacement for human intelligence and creativity.
I like to say, AI is the duck programming duck I always wanted
LLMs are the insensitive Asmovian robots I’ve always wanted, who translate and do the hardest part of my job: ensuring my emails are polite and none of my true thoughts or feelings are revealed…
Now I just need a way to protect my chats from any potential discovery, and business’ll be easy.
Re: Redis array: short story of a long development process
#8On safari mobile it's a page with the title header and a footer. Theres no content rendering.
Re: Redis array: short story of a long development process
#9It feels like Redis is becoming a small database, which seems to make it more convenient to use. Could you add more examples that clarify where the boundary should be?
Re: Redis array: short story of a long development process
#10It feels like Redis is becoming a small database, which seems to make it more convenient to use. Could you add more examples that clarify where the boundary should be?
Well, Redis is a data structures server, and has very complicated and edgy data structures like the HyperLogLog, so I have very little doubts that a fundamental data type like the Array will fit :) Also the actual complexity added is mostly two C files that are quite commented and understandable.
wc -l t_array.c sparsearray.c
2012 t_array.c
2063 sparsearray.c
4075 total (including comments)
A quick note: if we focus only on that part of the implementation, skipping tests and persistence code which is not huge, 4075 lines in 4 months are an average of 33 lines per day, which is quite low.