On safari mobile it's a page with the title header and a footer. Theres no content rendering.
Checking, thanks. EDIT: works very well on my iPhone, so without being able to reproduce is not easy to fix.
Redis array: short story of a long development process
11–20 of 118 posts
Re: Redis array: short story of a long development process
#12On safari mobile it's a page with the title header and a footer. Theres no content rendering.
[dead]
Re: Redis array: short story of a long development process
#13Let's make it very clear - this is the original creator of redis, or one of them.
He is not "your avg dev" and it took him 4 months with llm.
This is not a seal of approval for you to go and command all your developers to move to Claude code/codex/any other ai coding tool fully.
I'm looking at you - any avg CEO of a startup.
Re: Redis array: short story of a long development process
#14Re: Redis array: short story of a long development process
#15It 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) Sure there are also the AO…
I’m a big fan of your work, and I honestly didn’t expect to receive a reply from you. Thank you.
Also, thank you for pointing out exactly where I was misunderstanding the issue.
In the past, I used Redis for temperature measurements in a smart farm project. I used Hashes back then, but it seems like Array would fit that use case much better.
This looks like a very useful feature. Thank you again for the reply.
Re: Redis array: short story of a long development process
#16Is this an apologia since the PR is +22,212 -34?
Re: Redis array: short story of a long development process
#17Is this an apologia since the PR is +22,212 -34?
Haha, ~5000 LOC with comments. The rest is tests + TRE code + TRE tests.
Re: Redis array: short story of a long development process
#18Earlier quoted context omitted.
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) Sure there are also the AO…
I’m a big fan of your work, and I honestly didn’t expect to receive a reply from you. Thank you. Also, thank you for pointing out exactly where I was misunderstanding the issue. In the past, I used Redis for temperature measurements in a smart farm project. I used Hashes back then, but it seems like Array would fit that use case much better. This looks like a very useful feature. Thank you again for the reply.
I appreciate your kind reply as well :)
Re: Redis array: short story of a long development process
#19Earlier quoted context omitted.
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.
I occasionally type into slack "Future lawyers, the previous conversation is a joke. No one is doing cocaine to get through writing requirements docs."
Re: Redis array: short story of a long development process
#20Sharing my current MO:
I start with a high level design md doc which an AI helps write. Then I ask another AI - whether the same model without the context, or another model - to critique it and spot bugs, gaps and omissions. It always finds obvious in hindsight stuff. So I ask it to summarize its findings and I paste that into the first AI and ask its opinions. We form an agreed change and make it and carry on this adversarial round robin until no model can suggest anything that seems weighty.
I then ask the AI to make a plan. And I round robin that through a bunch of AIs adversarially as well. In the end, the plan looks solid.
Then the end to end test cases plan and so on.
By the end of the first day or week or month - depending on the scale of the system - we are ready to code.
And as code gets made I paste that into other AIs with the spec and plan and ask them to spot bugs, omissions and gaps too and so on. Continually using other AI to check on the main one implementing.
And of course you have to go read the code because I have found it that AI misses polishes.