Control the Ideas, Not the Code
antirez.com
Control the Ideas, Not the Code
1–10 of 208 posts
Re: Control the Ideas, Not the Code
#2I tried really hard to do this, but it turns out the models don't care about your ideas and want to do what's popular in their training data, so they will happily ignore anything you try to force down their throats, especially as context length grows or if you hit compaction.
So to make best use of the models steer them down familiar paths, mention common pattern and frameworks, use popular packages and languages that have the high median quality online.
I started my project with a few simple interface definitions and a short design / architecture doc that I include in the AGENTS.md file, but no matter how hard I try all of the models just end up ignoring it and sprinkled new seeds of variants of the same stuff all over my code base, that with each new session grow new branches.
Re: Control the Ideas, Not the Code
#3As a reminder, Redis was widely replaced by its non-vibe-coded fork Valkey.
Re: Control the Ideas, Not the Code
#4Follow the vibes
Re: Control the Ideas, Not the Code
#5As a reminder, Redis was widely replaced by its non-vibe-coded fork Valkey.
Do you have any evidence for Valkey "widely replacing" Redis, instead of just rapidly gaining adoption as well? Additionally, it's important to clarify that the replacement was 100% over licensing issues — iirc predating the vibe coding entirely — not the use of AI to code, and that furthermore, no one has to my knowledge pointed to any flaws in the Redis codebase even correlated with AI use. So this is a disingenuous framing.
Re: Control the Ideas, Not the Code
#6As a reminder, Redis was widely replaced by its non-vibe-coded fork Valkey.
Do you have any evidence for Valkey "widely replacing" Redis, instead of just rapidly gaining adoption as well ? Additionally, it's important to clarify that the replacement was 100% over licensing issues — iirc predating the vibe coding entirely — not the use of AI to code, and that furthermore, no one has to my knowledge pointed to any flaws in the Redis codebase even correlated with AI use. So this is a disingenuo…
100% of the employers I worked for since the time of Valkey had replaced Redis with Valkey.
Re: Control the Ideas, Not the Code
#7As a reminder, Redis was widely replaced by its non-vibe-coded fork Valkey.
I think that's a very unfair characterization. The Valkey fork happened due to licensing changes in Redis in early 2024.
Re: Control the Ideas, Not the Code
#8As a reminder, Redis was widely replaced by its non-vibe-coded fork Valkey.
Do you understand Redis and ValKey have mostly overlapping code bases? And of that intersection, a big part of the code was written by myself by hand. So no, that's not the case. Also as I wrote in the blog post, Redis is currently not using AI if not as AI-assisted coding. Of course I'm not writing this reply for you, since I believe if you write a comment like that, you are part of that HN slice that makes this site at this point a slop place (no need for AI for very low quality), but for others that may find this information useful.
Re: Control the Ideas, Not the Code
#9As a reminder, Redis was widely replaced by its non-vibe-coded fork Valkey.
As a reminder, Amazon and Google pillaged the Redis project and took all the profits of themselves.
OSI purity is hyperscaler brainwashing. They don't want to pay you. They want to take your labor.
Amazon and Google have made billions of dollars off of Redis while the original authors and the company formed around it have gotten none of that.
The best licenses for new database projects are fair source and open core.
Tell the hyperscalers, "fuck you, pay me".
Fuck valkey. Fuck Amazon. Fuck Google.
They're fucking thieves. And they'll lay you off the second they get the chance.
Re: Control the Ideas, Not the Code
#10Earlier quoted context omitted.
Do you have any evidence for Valkey "widely replacing" Redis, instead of just rapidly gaining adoption as well ? Additionally, it's important to clarify that the replacement was 100% over licensing issues — iirc predating the vibe coding entirely — not the use of AI to code, and that furthermore, no one has to my knowledge pointed to any flaws in the Redis codebase even correlated with AI use. So this is a disingenuo…
100% of the employers I worked for since the time of Valkey had replaced Redis with Valkey.
i am currently working on this exact migration at my company. aws also kind of pushes valkey so ppl seem to choose the default.