Sharing 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.

Thanks for adding this. Excited about array/regex, also very interested in your experience using LLMs to stretch your abilities. There are many of us laboring quietly on various projects attempting the same. "Vibe coding" (and the backlash) doesn't really capture how we work.

Let'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.

Thanks for the write up. Always interesting to see how very senior developers interact with AI these days.

@antirez: Introducing a regex feature that late into the project for a seemingly unrelated feature feels a bit weird? Can you explain more your rationale on that? thanks!

I vibe coded up an interactive playground against a WebAssembly build of the new array features: https://tools.simonwillison.net/redis-array

Closely matches my own experiences with current SOTA AI. Extremely useful collaborator, far from being a replacement for human intelligence and creativity.

It 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?

On safari mobile it's a page with the title header and a footer. Theres no content rendering.

Is this an apologia since the PR is +22,212 -34?

Is 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?

Got few questions:

- the project essentially spans almost 3 different (albeit minor) generations of LLMs. Have you noticed major differences in their personas, behavior, output for that specific use case?

- when using AI for feedback, have you ever considered giving it different "personalities"? I have few skills that role play as very different reviewers with their own different (by design conflicting) personalities. I found this to improve the output, but also to be extremely tiring and to often have high noise ratio.

- when did you, if ever, felt that AI was slowing you down massively compared to just doing it yourself (e.g. some specific bug or performance or design fix)? Are there recurring patterns?

- conversely, how often did AI had moments where it genuinely gave you feedback or ideas that would've not come to you?

- last: do you have specific prompts, skills, setups, etc to work on specific repositories?

[dead]

AI is a fantastic co-pilot, but you still need to know how to fly the plane when the edge cases start hitting the fan.