When vibe coding goes viral (Interview)

27 Jun 2025 · 1 h 11 min

Ask about this episode

Ask anything about it. ChatGPT or Claude reads this page and answers with the times it was said.

Connect VO and ask about every podcast you hear, including the moments you saved. Add to ChatGPT · Add to Claude

In short

Podcast Episode Notes: When Vibe Coding Goes Viral (Interview with Chris Anderson)

Overview In this episode of The Changelog, hosts Jared and Adam interview Chris Anderson, a prominent figure in the NoSQL movement known for his work with CouchDB and Couchbase. Currently, he is focused on Vibes.diy and Fireproof, tools designed for rapid app generation and sharing.

Key Topics Discussed

  • CouchDB and Couchbase: Chris shares insights from his experiences during the early days of NoSQL databases and how these platforms were established.
  • Vibe Coding: The concept of vibe coding is introduced, highlighting its focus on making programming more accessible and enjoyable.
  • Vibes.diy and Fireproof: These platforms enable users to generate apps quickly with a strong emphasis on ease of use and collaboration.

Key Concepts

CouchDB and NoSQL

  • Origins: Chris discusses CouchDB's development, which was inspired by frustrations with existing systems like Lotus Notes.
  • Community: The collaborative environment that led to the inception of CouchDB and later Couchbase was crucial in shaping its success.

Vibe Coding

  • Definition: A new paradigm that aims to simplify programming, making it more approachable for everyone, particularly non-developers.
  • Focus on Ease of Use: Chris emphasizes that programming should not be difficult, and tools should cater to those without extensive coding backgrounds.

Vibes.diy

  • Rapid App Creation: Vibes.diy allows users to create and share apps in minutes.
  • User Experience: The platform simplifies the development process, often allowing users to deploy apps without needing to understand deep technical concepts.
  • Community Engagement: Encourages users to share their creations and collaborate with others easily.

Fireproof

  • Unique Features:
  • Built as an embedded database that runs in the browser.
  • Offers end-to-end encryption and cryptographic data provenance.
  • Designed to provide a lightweight, efficient experience for app creators.

Monetization and Business Model

  • Subscription Model: Vibes.diy offers a competitive pricing structure aimed at making the tools accessible to a broader audience.
  • Token-Based Usage: Users may incur costs based on the tokens consumed while using advanced features of the platform.

Notable Quotes

  • "Programming is way too hard. It shouldn't be a thing." - Chris Anderson on the need for simplifying coding.
  • "We aim to be the right tool for those who want to show their friends how to code." - Chris Anderson describing the target audience for Vibes.diy.

Current Developments

  • Emerging Features: The conversation hints at upcoming features that will enhance community engagement and allow for more interactive app creation.
  • Focus on Education: Chris expresses excitement about educating people on the joys of coding and creating.

Conclusion Chris's journey from CouchDB to Vibes.diy encapsulates a significant evolution in the software development landscape, emphasizing community-driven innovation, accessibility, and joy in coding. The episode highlights the potential of Vibes.diy to become a transformative platform for aspiring developers and casual users alike.

Call to Action For more information, visit [Vibes.diy](https://vibes.diy) to start creating your own applications effortlessly and join the vibe coding movement!

Written by AI. May contain mistakes. Listen to the episode to check what was said.

Hear the part that matters, and keep it.Open this episode in VO. Double tap your headphones to save a moment as you listen.
Get VO free

Transcript

Automatic transcript. May contain errors.

0:05What's up friends, welcome back. This is the changelog. We feature the hackers, the leaders, and those who are vibe coding. Today, Jared and I are joined by Chris Anderson, a name you may recognize from the early days of CouchDB and Couchbase. So back when the world was just waking up to no sequel, Chris was at the center of it all, helping to shape how developers think about distributed data, offline architectures. And now Chris is working on Vibes.DIY and Fireproof, where one-shot app generation is a reality and shareable with friends in minutes. A massive thank you to our friends and our partners over at Fly.io.

0:45Launch your app in five minutes. Learn more at Fly.io. Okay, let's vibe.

1:00Well, friends, Retool Agents is here. Yes, Retool has launched Retool Agents. We all know LLMs, they're smart. They can chat. They can reason. They can help us code. They can even write the code for us. But here's the thing. LLMs, they can talk, but so far, they can't act. To actually execute real work in your business, they need tools. And that's exactly what Retool Agents delivers. Instead of building just one more chat bot out there, Retool rethought this. They give LLMs powerful, specific and customized tools to automate the repetitive tasks that we're all doing. Imagine this. You have to go into Stripe.

1:41You have to hunt down a chargeback. You gather the evidence from your Postgres database. You package it all up and you give it to your accountant. Now imagine an agent doing the same work, the same task in real time and finding 50 chargebacks in those same five minutes. This is not science fiction. This is real. This is now. That's Retool Agents working with pre-built integrations in your systems and workflows. Whether you need to build an agent to handle daily project management by listening to stand-ups and updating JIRA, or one that researches sales prospects and generates personalized pitch decks, or even an executive assistant that coordinates calendars across time zones.

2:23Retool Agents does all this. Here's what blows my mind. Retool customers have already automated over 100 million hours using AI. That's like having a 5 ,000 person company working for an entire decade. And they're just getting started. Retool Agents are available now. If you're ready to move beyond chatbots and start automating real work, check out Retool Agents today. Learn more at retool.com slash agents. Again, retool.com slash agents.

3:20Yo other no sequels your tech is a wreck like a oil spill. You call that web scale? More like toy scale. Your mimmap file is a database fail and your user's going to set sale for the one they can trust. Because if you're super yus, then you must be running Couchbase. Wow. Wow. Yeah, man. And it turned out to be true. It turned out to be true. That's a nice, it's nice when you put together a wrap and it turns out to be true as well. You know, it's like a bonus. Yeah, I feel like it's been literally 15 years though since that moment. Almost 15 years, right? Right. 15 years of focusing on the same thing in a lot of ways.

3:58And what we're doing with vibes is an outgrowth of that. What is that focus? If you could just put a name on it, what are you focusing on? Programming is way too hard. It shouldn't be a thing. Like if you're me, code is never the hard part and I want it to be that way for everybody. And how are you doing that 15 years ago with CouchDB and Couchbase? Well, my role over there was the Couch app side of the project, which was to make CouchDB into this serverless application runtime. You could just drop some JavaScript into and go. Did you get that done? It was, it kind of still is, responsible for a lot of people who otherwise wouldn't have had infrastructure to support them, being able to do things like rural health care or fun apps for their club.

4:45a lot of the same things that we're seeing people do with Vibes DIY. So for our listener catching up, Chris was first on the show episode 54 back in 2011. CouchDB, which is, I assume it's still a stance. You have to forgive me, Chris. I'm not out there using it, but was a massively popular open source database. Businesses formed around it. Damien Katz was the original creator or was it a group of people? I mean, there's a lot of people on the Wikipedia page, but help us understand the culture there. Damien's the guy who CouchDB came to in a dream, essentially. He had been working at Lotus Notes and getting frustrated with the fact that it had to pause the world to do its synchronization.

5:31So he invented the data structure that allows the streaming synchronization with fairness. And how did you get involved? I started using it to spider the web this was like early early on and had to teach myself Erlang essentially so I could drop a debug log function in there for myself next thing I know I'm through the whole stack and never looked back nice so what'd you do reach out to Damien say hey I'd love to help out or let's start a business or what how'd that whole thing come together? All good things start on IRC. That's a great answer. We were hanging out on IRC. I think it was Jan Linnert who came out to Portland for OSCON, like we were talking about.

6:16You know, we were already buddies from online. And then after that, Damien invited the Brain Trust out to his place in Asheville, North Carolina, where I said, hey, let's start a company. So my role in that, besides not being scared of the code, was not being scared of the lawyers. tell the story of that company from there tell the story like so as long or as short as you want it to be there's a lot that went on but the thing that really um sticks with me is the fact that we kind of accidentally incubated node.js we had you know people like isaac schluter and ryan doll hanging around the office, mostly because of Michael Rogers, rest in peace.

6:59And it was, you know, that crowd that was just informally writing NPM at the desk next to me. So really fun to be, you know, in the presence of greatness for so long and to be able to incubate things like PouchDB, et cetera, kind of taking JavaScript to the next level. So my first exposure to CouchDB was via a, now we're name dropping, a Jeffrey Grozenbach peep code on CouchDB. And he made it look so cool. I was just a fledgling Ruby on Rails developer, of course, dipping my toes into the JavaScript ecosystem. And kind of exploring databases at the time and like wondering. Because Rails made it so easy to kind of switch your database adapter, but nobody's really doing that.

7:45but I was interested in the different databases and like CouchDB was so radically different than what I've been using. And yeah, Jeffrey's voice, which is epic to this day. Legend. Yeah, he's a legend. Made CouchDB look like this is where the cool people are coding. And it turns out it was true. I mean, from your story is like, yeah, a lot of very talented people are involved in the project. You have to remember 2008, 2009, that was the very beginning of the API revolution. You know, the idea that you could put your database behind a REST API, almost nothing was even JSON yet. So we were all frustrated with XML.

8:26We were all, you know, writing kind of monolithic servers. And by the time that project kind of matured, even as early as 2011, at least the, you know, early adopters were already doing microservices. And so it was really that was a big sea change right then. Was it good business, too? I mean, you started a business around it. Was the business good? Was it hard? How'd that go? It was good and hard. And in some ways, we brought like a cultural cachet that allowed us to, as we discussed, like on episode 54, merge with Membase, who had a whole bunch of really smart people who understood the market and how to drive a startup to success.

9:11So, you know, Steve and me, who I learned revenue from over there is now on the board of Vibes DIY and helping me do the right things here. It took a while, but they IPO'd. They IPO'd about five years after I left and, you know, always watching it real close. So what's your journey from leaving there to Vibes, Vibes.DIY, which is your current thing? Well, I bounced around a little bit, you know, checking out other database technologies, worked on FaunaDB, which I still maintain has some of the strongest integrity that you can get. Then I went to McKinsey and Company. Kind of a fun story there.

9:51Like, you wouldn't think that. Oh, yeah. My whole family was like, really? Yeah. And the, but, you know, Jason Smith is another legend. He's still there. but he brought me in and his his claim to fame is well for couch he hosted npm so npm used to have a one-man host and it was him and uh and yes so great to have him show me what the real world is like and what i learned about the real world is you don't get infrastructure right us here in the silicon valley culture where we can you know boot a virtual machine or request an s3 bucket and get it. Like that's just an unbelievable luxury. What I learned from this constrained environment of the client doesn't know what cloud you're going to use until it's too late is I need to build a database technology that can run anywhere to allow permissionless innovation.

10:47And so that's the gem of what became Vibes DIY. I built a deep tech thing along with Michael Rogers team at Protocol labs who did a whole bunch of research on immutable data structures with content addressing. I joined that team for a little while and saw the potential of it and built an embedded database that runs in the browser with end-to-end encryption for multi-user synchronization. And that's what powers Vibes DIY. The database is called Fireproof. Basically, everything I'll talk about today is open source. But if you want to get into Fireproof, there's plenty about it. The thing that it does uniquely is give every operation cryptographic data provenance.

11:34It's almost like a mini blockchain in the browser. Super lightweight, no network dependency, just runs right there. But it means that when you do a replication, you know what you've got. There's not questions about what kind of data you're sitting on. Let's dive into that. When you say cryptographic data provenance, what do you mean exactly? So it goes back to Rich Hickey, Clojure, and the immutable data structures that they were pioneering around the same time we were doing Couch. And what you see in those data structures, as soon as you have an invariant that you're working with immutable backing storage, you have to do everything different, everything new.

12:12with fireproof and the IPLD data structures that it uses. That constraint is enforced because the only pointers you're allowed to use are hashes of content. And so everything is addressed by its own hash. That means you can only talk about stuff that's already been written. And that means that every time you're doing these B-tree like updates, you're either going to churn data in a real heavy way with you know lots of kind of right amplification that's unnecessary or you're going to solve these hard hard problems that the research team over there people like alan shaw and volker mish worked on where you have trees that have really interesting properties so what you what you need and which is a lot of work to get is something that is a search tree, like a B tree.

13:07But regardless of if you put all those records in, in one order or a random order, you still get the same root hash at the end. So your snapshots have stable identifiers. And that means your replication doesn't have to be mechanically the same everywhere. It means you can replicate essentially in an optimized efficient way, but still end up at the same end point. so fire fireproof fire store what's it called fireproof fireproof is this your implementation of these concepts or it's my essentially um making it so easy to use you know we talk about technology especially databases and one of the phrases people like to say is a foot gun right a foot gun is when if you don't do everything exactly right it blows up on you and the requirement I had for this technology is no foot guns.

14:02It's literally designed for the code school dropout. Okay. So you can't actually shoot yourself in the foot. Right. And that turned out to be the right place to be because we got a lot of people vibe coding. Well, even more than that, I'd say with LLMs and GPTs and all that, we have an infinite supply of code school dropouts. Oh, true. Yeah, exactly. Where they are infinitely supplied depending on how much money you have, right? There's another one there. Assuming you can afford those tokens. So you're working on Fireproof, you're building this, making it simple for people to build things with it.

14:40And then where does Vibes DIY come into the story then? So we were going to market with Fireproof after the technology got mature. And there's use cases like black box recorder for self-driving car, like things that are very serious that are served well by this content addressed immutable data structure but there's not very many people who need that and they don't care how easy it is right that's a different set of problems for them when we started to see in our discord people coming in saying i haven't programmed in 15 years but i built this drum machine along with chat gpt and your api and it worked right out of the box we realized we've got vibe coders and so i brought in a old friend of mine this guy marcus estes who i've known for like 20 years and he's just a hustler right he makes it happen he understands where the opportunity is and how to go after it i've been looking at this vibe coding stuff thinking that's fun that's cute he realized like no let's just do this and uh we didn't look back So it's been so much fun.

15:48The big difference, like the real difference that matters is my kids who were so sick of hearing me talk about Merkle CRDTs and all this stuff. Now they're grabbing my phone out of my hand, right? That's cool again. You know, they just want to, they just want to make apps. They're like, dad, can I make an app? And you know, can I make another Merkle tree? You know, right. What kind of apps are being built with this thing or can be? Well, I was really inspired. I was trying to see, you know, essentially what's the lowest common denominator that we can address. And the answer to that is I was using ChatTBT Canvas and Cloud Artifacts and thinking about how for like a normie, somebody who doesn't already know their way around the next JS stack or, you know, deeply understand React and all the tool chain there.

16:42Those are the best kind of interface and set of metaphors. If you look at those closely, they don't even say deploy. They say publish. And so that's the take we've done with Vibes DIY is if when I'm designing a feature, if it's going to require introducing a new concept, don't. Right. Just make it simpler. And we had this tremendous validation. We just got back from RenderATL. ATL, it's a tech conference in Atlanta, where we had a deep line at the booth, you know, crowded up with people who had kind of maybe never even heard of Vibe Coding, or if they had, they hadn't tried it yet, or if they had tried it, they thought the existing tools were too complicated.

17:30And when we said, hey, if you make an app, we'll install it on this sticker for you, they would spend the 90 seconds it takes to make an app. Wow. What's on the sticker? Is it like a QR code or install it kind of thing or launch it? The way we install it in here is with the Near Field Communications chip. Okay. I actually learned about that at like a Burning Man event where someone was doing manicures with NFC chips in them. Really? Yeah, which is super hot. Like, here's my number. Right. Like you can just embed a little bit of information on that chip and then carry it around in your fingernail.

18:13Yeah. That sounds very burning, man. Yeah. Yeah. You learn a lot. You never know where you're going to learn a lot. Here's your next big idea. Right. Wow. So what. So if I take the sticker home. How can I use it? Like I got this information embedded in it. What do I do? you just kind of get it close enough to your phone and you get one of these little and now you can open the url okay so similar to a qr code except for not for the camera but actually the nfc chip in the phone makes sense that's right and for us it's really this ownership metaphor like code is all in there over there especially if you're not a coder like what am i making where is it but if i put it in your hand when you walk away from the booth then you're going to come back with your friend the next day.

19:01Does that give them access to the code they just created or vibed or does that just give them access to the application they just vibed? Well, for us really are... Like consumer development, how they keep going. You're totally right. So most of these people made it on their phone they walked up to the booth with because it's a mobile first experience. But if you didn't, if you made it on my phone or if you made it on the booth laptop, then you still get the sticker. You can still scan it into your phone and anyone who goes to a vibe can hit the remix button in the corner and get into the code or get into the chat and say you know the the default remix we have pre-loaded in our in our form is make it pink but really just whatever you want to do to change it change um there's a great story we had a lot of fun um i was walking back from lunch in atlanta and i said i said to my phone i said i want to take pictures and have you turn all the faces in the pictures into georgia peaches and it worked on the first try you know sometimes you get lucky and people thought that was hilarious so we were showing it off and then um you know we were sharing a booth with netlify they're great friends of ours and one of the one of the netlify leaders uh sean brought his kid and so she saw what we were doing and she said i want to be a cat

20:26basically a four-year-old turned the peach app into the cat app and that was a hit and then we saw what was going on there and we made this um we made a caricature app i've got on my laptop here here's me as a podcaster and uh you know and it was it was also a big hit people at the conference just all day long building stuff. Just fun. Wow. That's the stuff I'm talking about, Adam. Just for joy. Total vibes, man. This is the internet, man. It's for the joy of it. It totally is for the joy. And so many people - This is like GeoCities for the modern era. Seriously. It's like a writable GeoCities, right?

21:00Yeah. View source is back, baby. Yeah. I'm reminded of the old cloud to bud extension. You guys remember that one? Every time the word cloud was on our website, this Chrome extension would replace it with the word bud. But I'm not saying this is an idea for a remix, Chris. I'm just saying I'm reminded of it. You know, I should, if I, if I didn't, wouldn't get distracted. We'll just build it right now.

21:35Well, friends, it's all about faster builds. Teams with faster builds ship faster and win over the competition. It's just science. And I'm here with Kyle Galbraith, co-founder and CEO of Depot. Okay, so Kyle, based on the premise that most teams want faster builds, that's probably a truth. If they're using CI providers with their stock configuration or GitHub actions, are they wrong? Are they not getting the fastest builds possible? I would take it a step further and say if you're using any CI provider with just the basic things that they give you, which is if you think about a CI provider, it is in essence a lowest common denominator generic vm and then you're left to your own devices to essentially configure that vm and configure your build pipeline effectively pushing down to you the developer the responsibility of optimizing and making those builds fast making them fast making them secure making them cost effective like all pushed down to you the problem with modern day ci providers is there's still a set of features a set of capabilities that a ci provider could give a developer that makes their builds more performant out of the box, makes their builds more cost effective out of the box and more secure out of the box.

22:51I think a lot of folks adopt GitHub Actions for its ease of implementation and being close to where their source code already lives inside of GitHub. And they do care about build performance and they do put in the work to optimize those builds. But fundamentally, CI providers today don't prioritize performance. Performance is not a top-level entity inside of generic CI providers. Yes. Okay, friends. Save your time. Get faster builds with Depot, Docker builds, faster GitHub action runners, and distributed remote caching for Bazel, Go, Gradle, Turbo Repo, and more. Depot is on a mission to give you back your dev time and help you get faster build times with a one-line code change.

23:31Learn more at depot.dev. Get started with a seven-day free trial. No credit card required. Again, depot.dev.

23:44So is the platform the web then? Or like, how are they, how are these things running? That's the way I think about it. I wanted to build the experience I had early on in, you know, the black and white Mac days with HyperCard. But I realized that when I look around people trying to build similar ambitions, often there's a do it our way completely or don't kind of feel right i call that like they make you wear the socks with us the point is there's already so much platform that's done so we just build react apps and we're essentially taking the web runtime right which is like what a browser can do and making it as easy to express yourself there maybe easier than making a tiktok so if making an app is easier than making a TikTok.

24:37Now what? And that's the question Vibes DIY is out to answer. I love it. I think Adam and I were just talking about this new possibility, specifically in light of Apple allowing local models on phones and Xcode and like things are getting localized there where it's like you could build and deploy your own iPhone app. It's just a one-off just for you. Nobody else even has to have it. And there are still like platform limitations there with regard to distribution and, you know, side-loading. And there's like lots of stuff. But like with the web, it's like, nah, just URL, you know, publish that sucker.

25:12And that's really awesome. So just to nerd out again on the sticker, is the embedded information in the sticker just a URL to where the thing actually runs? Or is there code in there? Or how does that work? It's just the URL. So once you have the URL, we make, it's actually our service layer so simple. We have your, so if you look at a lot of the existing Vibe coding tools, they're built for professionals and they're going to like mimic a professional output with a full Next.js app. The only thing that the model, which is just a commodity model, we have a switcher. It's actually a great way for, you know, AI interested devs to try out all the different models and get their personalities down.

25:52But when you ask Vibes to make something for you, it's only writing app.jsx, and that's it. So our focus is on being fun, done, and alive with AI. This last bit means that the apps that you make get the same API key that we use in your browser to write the code. And you press the demo data button, and it fills out your to-do list with whatever is plausible. or it makes an app i built this because it takes 90 seconds to make an app it takes longer to figure out how to use an app so instead i just mash the demo data button and it shows me what the app would look like if you'd spent some time in it so let's say i mash out a 90 second thing and it's rad and we're having fun can i then expand extend like build that sucker out or do i have to remix and start something else that's where our one of our core values comes in is that it has to be real.

26:49So the 500 lines of JSX that it's going to write is React code. It's as good as Cloud4 is going to make it, which means it's not that bad. And the standard library we bring to the table with it means that all these apps are fully functional just in the browser, but then they can be remote synced via the cloud to other users for collaboration. And that means copy that. There's a copy button. You get your 500 lines of code in your clipboard and you go drop it into anywhere and you know maybe into a vite template or maybe into another vibe coding tool and say hey expand this maybe you turn it into 10 pages maybe you take 10 vibes and put them into one app but there's the sky's the limit it's really fully malleable software that pros can take and run with as well as beginners can just use Adam what do you think of all these sayings he has he got like rhyming words he's got like stickers a poet man this guy's bringing it.

27:46I'm over here trying to vibe over here. I think it might be a Safari issue. I thought you might be. That's why I pulled you back in. I'm like, I can tell when Adam's like testing something out. I was, I was vibing over here and I think I might have hit an issue with Safari potentially because the thing it made me is on a black screen and so I'm having an issue. That's not Safari. That's Claude. I would say you got, you rolled the dice and you got a snake eyes. Oh, dang. One in 20 times. And one in 20 times Claude is like, oh, I know what you want. a black canvas that's like 20 times bigger than your screen.

28:19It just does that. We have work to do. Yeah, I think that's about it. It's kind of like forever scrolling. Close the tab and open a new tab and try again. I can share with you my it was just intense, man. This is an intense process. I saw it write a bunch of code. I could steal the code, but there's no application to be viewed. Basically copy that prompt you did and just make a new one. That's what we learned from vibe coding. like don't go iterate on something unless you're already stoked about it all right yeah it's just cheaper to throw it all away and start fresh right yeah right i mean when it's just spoken word it's like let's try again and just tweak a little bit you know that's kind of what i do remember with google searches remember when you used to google things you know some people will put in a search and then they'll like read the results and if they're if there's not the right answer they'll go to like page two, page three, page four, you know, like an infidel.

29:12I just research, right? Like, well, my search wasn't good enough. I just research. Now I have the same thing with these LLMs. I just take, I just copy prompt into like four of them. And I'm like, let's see who's got the best answer or the fastest or whatever, or I can like mentally munch them into one answer and like pull things from each one. And that's kind of the new research is just like, nah, I'm not going to like tweak this prompt. I'm just going to try it on more things and see what happens. So yeah, close tab, open new tab, you know, paste prompt and start vibing again. Yeah, we're considering seriously doing that for you.

29:48We may as well just vibe three of them in parallel and let you pick the best. Although every bit of complexity we add, you know, is going to take the simplest user and turn them away. And cost. I mean, that's what Sora does, which is OpenAI's video tool. You know, you can pick how many different iterations that you want and it will make two or four or six. Obviously, you have to have the tokens and stuff. But especially with creative tools where it's like, I would like to see four different things. It's just like, yeah, we'll just crank out four versus you having to say, you know, try again, try again, try again.

Read the full transcript

30:20The fun part is looking at how much better Claude 4 is than even 3.7. or if I switch it over to Codex Mini, then I'll get like an app that works great, but isn't showboating at all. Like GPT models make these lean apps with no extra stuff. And Claude 4 is gonna have your like backgrounds, transparency with blur and moving. It's fun to see the personality in there. I think Claude 4, and I don't have any personal reason to say this in terms of like, we're not making money by promoting Anthropik, But Cloud4 is just, I think, good enough now that it's sold me on the entire thing, whereas up until now I've been very skeptical because the results have been so bad.

31:03I'm not sure if you guys saw Simon Wilson's the last 12 months of LLM progress as outlined by Pelican's writing on bicycles. You guys see that post? Oh, yeah. Because he's such a nerd for every new model that comes out. he tells them all to do the exact same thing which is to write a code that produces an SVG drawing of a pelican riding on a bicycle and he documents that of course because he documents everything and he's just showed the progress here's this model, here's that model all the way down through the last year and how far they've come and which ones do better and he scores them and stuff like that but the progress has been amazing and Claude 4 I think we're at a point now where it's like above my threshold of sucking to where it's like, let's do it.

31:51Like, I want to use them now. I'm not sure what happened between 3, 7, and 4, but something happened. That black screen that you ran into, Adam, the other one that I'm just still trying to, you know, teach Claude to never do again, for some reason it loves to give you buttons with white text on white background. Oh, dark patterns. The opposite of dark patterns, light patterns. Did you get better results this time, Adam, or are you still? It's still working on it. It's a little slow for some reason. It's taking its time. It's a bleeding edge. How many lines of code does it want to do? At this point, it's trying again.

32:25So I got two black screens in a row, so I wasn't sure. What are you trying to build? Okay, so I told this thing, I want to golf with friends. Help me create a tea time and invite folks to it. So, hey, Jared, I'm going to golf this Saturday at this time. You're invited to my tea time, and you can join, kind of thing. So that's, oh, it finally did something. It's got a golf tee time organizer. I can create a new tee time. I can invite people to it, it seems. Looks like more iteration. It's got some additional features that could be added, which I think is kind of cool. But all in all, quite colorful.

33:03It's vibrant. It's got a cool vibe. It's vibing. This is vibing, man. This is vibing, man. Right. So do you guys like have a system prompter? I'm sure you have some sort of scaffolding in there that when we write our prompts and put it into Vibes, it does more than just that, right? The whole thing's open source. So you can go on GitHub on the VibesDIY.org and get into the repo prompts.ts and see what we actually do. But it's fairly simple. I mean, as I was mentioning earlier, I was one of the co-authors on the O 'Reilly ChatGPT shortcuts book. And what I learned from that and the experience continues to pan out.

33:42if you talk to the LLM like a person, you know, like less technical, more just what you want, you get better answers. So this golf thing is the thing you want to do. Um, there's a, there's this great YouTube. We can find it for the show notes. It's there's, you know, two, two types of vibe coders. And there's the one guy who's all frustrated with his 4 ,000 line LLM's text and his feature specification PRD. And the other guy who's just like, make GTA, make GTA 6 and he's having a briot you know here's my golf tracker oh nice did you do that one just now as Adam was doing one or is that yeah after I heard what he was doing and I think my prompt my prompt was just what is it again show it to me I said golf with friends oh that's all you said yep oh my gosh now okay so how do you share that with me so I can see it or play with it or you know remix and revive Pass the address into the chat.

34:41We have a chat here. Right? So, again, we don't deploy. You press the purple button, the big button, and now you publish it. And I was getting to this a minute ago. I guess I distracted myself. So when it publishes, all it does is take, like, let's say the 475 lines of JSX and put it in a Cloudflare KV associated with the subdomain name. When you go hit that subdomain, we have a static HTML that's essentially the runtime that's got all the packages in there and it loads any additional packages via ESM.sh. And now you have your app right there, costs us almost nothing to host, almost nothing to serve, unless that app goes and does some AI calls, in which case that goes against your token quota.

35:26So it makes it super easy for people to write these apps that are alive with AI, whether that's maybe our benchmark. If, you know, compared to Simon Willison, he's got the penguins on bicycles. What we have is, for instance, I'll just tell you something in English and you'll give me a structured to do list that reflects back what I need to do to accomplish that. So I'm always running that when we do an upgrade or move to a new model. and this morning i said take my kid to summer camp and it gave me everything sunscreen lunch all that all right i just loaded up adam's golf tea time organizer is it working i mean it rendered i don't know if it's actually working i think it has white has a white button with white text as chris something's going wrong here because i can't get the load for me but i can create a new tea time uh sweet oh i see some sunnyville golf and club i can join that round yeah pop your name in there boom okay i'm joining that round my name is jared thank you very much and uh confirmed jordan phillips is going and jared is going so where is it storing that information chris where does like the data that i enter in go so all that stuff goes into fireproof which has got that merkle crdt and that means that it just goes in your browser local storage the way fireproof works is every database operation is a diff, like in Git, that is end-to-end encrypted and then written to, we use IndexedDB in the browser because it's real fast with uint8 arrays, but then asynchronously can be replicated via S3 bucket and WebSocket.

37:05So that part works in Fireproof. We're rolling it out in Vibes right now. That means today all Vibes are single player. that's why it's best for these kind of viral ai experiences but tomorrow all vibes have essentially the security model of a google doc so i don't want an end user to have to understand like postgres row level security or you know having to do like where clauses to keep from writing bugs instead if you're in the app you're in the app maybe you have write access or read access but it's as simple as a google doc for the sharing and that means you know as soon as would activate that feature, then Adam, you could invite Jared to your app via email.

37:49And now y 'all are both in there, you know, setting up, what are you going to bring for lunch to the, to the course? And it's all on the web platform. Yeah. Yeah. No, none of the people who don't know what code is, who've never deployed anything, like they can't depend on any, you know, setup. I like to say, if you don't know what an API is, then I'm certainly not going to ask you to do an API key. So this thing went render ATL viral last week because I already had a fun time making caricatures of themselves. But when's it going to go, you know, TikTok viral or youth viral? Like it seems like this is set up specifically for 13 to 15 year olds to find out about it.

38:31Just like the 6-7 thing. I'm not sure if you guys are aware of 6-7, but they're huge on 6-7. And all of a sudden it's like this thing screaming. in. Well, I'm pretty sure that my key into that market is you guys.

38:47But really, what we aim to be, like there's a lot of people who use more serious tools for Vibe Coding, and I'm not going to try and be, you know, I'm not going to give a senior developer more control, more options, more details than other incumbents. But what I will do is be exactly the right thing that they're going to turn around and show their friends when they want their less technical friends to start getting into writing code so if you've got a buddy who has a dream or keeps bugging you to build something for them say hey vibe it up and i'll take it from there right well it's very much the geocities then in that sense or maybe glitch um of course glitch recently changed the way glitch works but similar vibes then right glitch was very much the thing where it's like get people started you know learn on it yeah how does versioning work in that multiplayer world?

39:39So if you look inside the chat that you've been having, you can refine it. You could say like, oh, you know, I didn't mean regular golf. I have these interesting rules of golf I want to bring to the game. Claude will go rewrite the code for that. Now you have a slightly different version of the app. That could be within a single chat session, in which case we're not remixing yet. We're just iterating. But if you go look in that chat, you can click on the older versions of the code and it brings them up instead. Whichever one is on your screen is the one that gets published when you click publish.

40:10So publish an old version if the new one wasn't as good But once it's published and you go to that URL, you know when you scan the sticker and you go to the URL Then you're gonna have a remix button in the corner of the screen and when you hit that you've essentially forked now No insult to all of the people out there who are kind of like me in this regard, but I've been forking forever and what we say to ourselves to make sure we stay on target at Vibes DIY is we say forks are for dorks. This guy's got a saying for everything. So because you don't like forks or because you do, I mean, it depends on if you think a dork is a good thing or a bad thing.

40:51Right. Well, when it's time to get the dorks involved, do the forking. But when you just want to try something and remix, right, then you don't need all that conceptual baggage. Just hit the remix button then go. So this is akin to the publish button versus the deploy, right? Like it's like remix it. Don't fork it. Cause you're not a dork. You're a normie, as you said earlier. Yep. Yep. Well, you know, your audience and it's not us. It's not us. Cause I'm looking for the fork button over here. I'm like, excuse me, sir. I would like to fork this. Totally. Well, it is us though, because when you go deep on something, it's got that Merkle CRDT it's made out of standard react components.

41:28It's got all the TypeScript annotations you could hope for, and it's ready to go big if that's what you want to do with it. But I imagine sitting on Cloudflare with an HTML file and some KV backends that big in terms of maybe features and commerce and production, big, business big, but not big in terms of scale. I imagine one of these could scale pretty easily in terms of that TikTok viral moment, couldn't it? It costs pennies on the dollar compared to anything that requires a VM or any kind of complex state or CPU. When I think of Kubernetes, containers, all that, I only want one if I basically want to rent some live RAM.

42:12Right. And you don't need that. All the live RAM lives in the user agent at the edge. So Cloudflare is pretty cool. I mean, just, you know, no further comment. I wonder if you could maybe expand on that. Like you guys are doing cool stuff because of what Cloudflare is helping you to do, right? I mean, that's just, it seems like a very interesting platform in that way. Our stack is, I guess, native to that way of thinking about things. So not just the publish flow that goes into a KV, but also the fireproof synchronization is powered by Cloudflare workers, which is a great way to rent some RAM on the cheap if all you need is a list of your currently connected clients.

42:56So essentially the flow is that tiny encrypted diff, you write it locally, push it up via our API, which you don't have to know about, but it ends up as another record in an R2 bucket and then an update to the pointer that corresponds to your database. so everyone who's listening to that pointer pulls down the latest and because it's a crdt the merges are resilient right i was thinking about recovery mechanisms say like you lost the pointer and all you had was the files it's a valid exercise to just load them all and merge them and you'll get the same result as if you started from the from the end one why ram why does it need to be in ram i mean it doesn't i just we can do it with s3 bucket it's cool right because it's a little faster to keep it on s yeah web socket and what i mean by inram is necessary though or is it just because it's cool it's just because it's faster right so we need essentially a directory a link to okay let's get technical the real reason we need any of that is because it's multi-writer safe and so if you just had like a sq light and you were trying to do this kind of architecture which people do where they put the sq light segments into an s3 bucket and then they load them in the browser and querium, that's all good until you need to start writing.

44:16And now you're doing some kind of bespoke, you know, take the write ahead log and put it in there and manage, you know, kind of conflicts against it and everything. It's not for the faint of heart. Instead, what we do because of this Merkle CRDT, the merges are handled for you. So the only thing we need to add to the recipe to make it multi-writer safe is it could be that pointer that points to the most recent file the diff from which you got to start to reconstruct well it can point to more than one file so if you're under concurrent load people can all you have 50 people all right on top of the same starting state without having coordinated each other yet and now we just have a pointer that's 50 wide the next read pulls those in merges and writes back up the single pointer so that's the that's what we do the performance thing for so in your mind or in your heart is fireproof the thing and vibes diy is a thing to demonstrate the thing or is vibes diy the thing that beat that fireproof let you build i feel like i'm in the millennial millennium falcon and i just like mashed the gas you know so it's a little bit of both but it's it's super aligned fireproof is for the kind of people who like to fork stuff and vibes for the kind of people who right don't want to be bothered with all that it's just done okay do you think you're gonna have to pick at a certain point or like focus or do you have infinite bandwidth to just like mash that mash that millennial falcon what's it called warp speed no they don't call it warp speed what do they call it in star wars i'm blanking the hyper drive yeah the hyper drive go to hyper speed so We are focused 100 % on Vibes.

46:02In a lot of ways, it's because Fireproof is basically done. I mean, it never is the case with a database, but it's not like it needs new features. It's just about hardening it and continuing to release it. So in that world now, Vibes gets cool new features, like a fun new feature we get to add. This is the lightweight stuff. It's like, like I said, I don't want people to have to know what an API is, much less an API key. So bake that YouTube API key in there. It's not in there yet, but this allows you to say, hey, I want to turn my playlist into a YouTube screen and it just works already. Same thing for Spotify or any other of these kind of mass market media APIs.

46:43There's no reason that you as a vibe coder should have to know about any of that to use it. Have we talked about money yet? How do you make money? No. Let's talk about that. Let's talk about it. Does it matter at this point or is it just for the vibes? It matters that we don't get it wrong. And then the more we think about it, the more excited we get. So if you look at what it would take to build something with like a vibe coding tool and a database backend, those are both kind of like maybe just to get started. Table stakes,$25 a month,$25 a month. That's$50 a month right there. We do an all-in-one bundle at$5 a month.

47:20And that's because all we need is that R2 bucket. It's not costing us a whole Kubernetes container to keep your Postgres instance running. Makes pennies on the dollar for us. And then the real cost becomes those tokens that either your app consumes when it's generating cool caricature images or parsing your to-do list, as well as the tokens that you use when you write an app. $5 a month gets you started. If you want to go over that, there's a meter, which is competitively priced. and then where we see this going in the long run is almost like this YouTube style model where say you know first think about a corporate case think about some big marketing agency that builds like see our product in your house you know replace the Statue of Liberty with our product whatever it is right take a photo put us in there that's um you get 100 ,000 views on that from your email list, you're probably writing us a check for$20 ,000 or something on the tokens it consumes.

48:23But if you're some kid who figures out a cool way to scan your house and turn it into a video game level, you don't have that kind of money. But your app costs just as much to run and it goes just as viral. So in that world, there's a little bit of a freemium. Somebody comes along, uses the app, they can generate a simple level or a couple of images, but then they're going to get through their set of free vibes tokens, if they like what they're experiencing, then now they're subscribing for$5 a month. So we're not just selling it to developers. We're selling it to people who want to make cool caricatures of themselves in their dream job or whatever it is that these end user apps do.

49:03And so now if you're that kid who made the cool video game and you don't have any money, but you get us 50 ,000 signups, then my goal is to write you a check like youtube does that turn your house into a video game level thing exist because i want that no somebody's got to make it i mean why wouldn't it exist such a good idea right gauzy and splat is cheap now running on the phone how would you do that though would you just walk around your house just like taking a video and uploading it i don't know how would you we like to say that um the best we can hope to do you know we're kind of grizzled old vets of the industry the best we can do is invent the electric guitar it's up for the kids to invent rock and roll that's like the best not answer ever right he's like you guys figure it out all right yeah i mean we've got roadmap features that expand so everything i've talked about is really just the browser runtime it can do a lot it's underutilized especially for people who don't really you know haven't haven't pushed it to its limits yet but yeah roadmap features is like something we learned from the couch db ecosystem, essentially Fireproof is the CouchDB model running in the browser.

50:13And one of the things that you see a lot of the way NPM was powered, all those packages stored in CouchDB. And then when someone uploads a new one or makes a change to some metadata or whatever, there's just an event reactor subscribed to the database feed that can then go do some heavy lift or send an email or update some analytics package somewhere. Same thing. Just if you wanted to today, you could stand up a Cloudflare worker that subscribes to that golf database. And when somebody puts in a new tee time, you get a push notification. Our roadmap brings that to the masses by making it so there's just a backend.js that we also let the model write.

50:54Yes, I wouldn't even thought about that, I guess. So it'd be helpful as a guide, you know, like here's the next step you could take. they can mention different features can come but not the not what you mentioned there which is like push notifications that'd be kind of cool right and there's no end to that kind of stuff and we really essentially if i think about the job you're hiring that back into dot js to do it's the stuff that you know essentially hiding api secrets there's you can't just publish the way that you send your emails your postmark key to the world you can't put it in the browser but you can put it on the back end and then the back end's job is just to forward those messages what happens when it's successful what is a year two years from now like how does this change things what is vibes.diy a year and a half from now well now that it's easier to make an app than a tiktok we picture people you know swiping right on the good apps and long pressing to launch it And, you know, having essentially, you know, their phone blow up in their hand when their app gets popular.

52:06So the same thing you see with an Insta or a TikTok or a YouTube where it's really about the excitement you get from coding. That's what I saw in Atlanta when I was first starting coding. Right. Like the coolest thing in the world was just to change, you know, some one line in your HTML and then hit refresh. and there it is. So educating people how that feels and then, you know, letting them share that with their friends. I think what we see is that coding becomes something that is cool. What do you, how do you deal with the potential of scams or just like security issues in that unfitted world where it's like, yeah, check out my Vibe app and it's cool.

52:48But like what happens when it's a scam there's thankfully a whole bunch of prior art essentially for us dev tool builders it's a little bit of alien land but if you've done social media before it's that playbook so we've done some of the basic things already for instance there's no way to publish to a fire hose it's not like just everything's all showing up we moderate the stuff that goes out on the home page that doesn't mean you can't share something and so if you start building honey pots then now we have a different moderation challenge it's not new it's just new to do it with html instead of video or images yeah i just want to like it's it's one of those things where you don't want to have to deal with it but you do and it's early because like trust will be everything to to get to the tiktok stage of sharing and viral virality or whatever it's going to be something you can trust or has to be.

53:44And if you can't trust it, then it's like, it's a today problem basically like at launch. Yeah. So if you look at the history of like using mechanical Turk to moderate profile images and having to do, you know, two of three thumbs down and all that, so much cheaper, so much easier to do that with a model now. Just let, let Claude tell you whether it's not any good, you know? And then on top of that, We aren't going to run into these problems to, it's sort of blunted. We don't give you the ability to go into the editor and type. It wouldn't be hard for us to, but we figure that's the point you should copy and paste it somewhere else.

54:23And Claude's not going to write something out of the box that's going to be extremely concerning. We just use the OpenAI image gen. It makes our job easier. Eventually, we'll want to value engineer all that stuff, but that comes with scale. Solve it with more AI. That's interesting. Right? All problems get easier with AI? Well, AI makes new problems faster than it makes the other ones easier, but hopefully we've isolated ourselves from that with this one file app.jsx thing. Yeah. And don't underestimate the power of the single origin policy. You know, the web browser kind of already worked out a lot of this stuff.

55:01So if this thing takes off, I mean, now's the time to get in there and really be the vibe DIYer in chief, right? Like the people that were early on YouTube, the people that were early to TikTok, they had a much better time. Is there actual virality built into it? Can I build an audience? Can I distribute? Is there a distribution channel? I know y 'all are just getting started, so the network effects probably aren't there yet. But are the tools to build an audience for my apps in the product? So if we're talking 90 seconds from prompt to app, you know, on the cases where it works, probably another 90 seconds to be like, is this app any good?

55:39And then hit publish. And now it's on a URL. So we go wherever URLs go. But the built in features around like a news feed and a for you page and all that. These are the things I'm super excited to build. we're growing the team right now people who want to do that should probably talk to me about it but it's definitely it's a kind of it's a kind of interesting green field because so much of the design language is already worked out it's not like we have to decide what an algorithmic feed even is it's more just about making it for basically we're bringing a new media object to the world and right the same thing you do with a video you do with this and we even have plans For instance, the same Jason Smith I mentioned earlier used to host NPM.

56:24I talked to him about it yesterday and he said, hey, I've been working on some video gen stuff. I think you could do like we have this demo data button that fills the app up with data for you. You could also do a video tour button. You just click one button and it takes your face, lip syncs, puts it on TikTok. Here's my app. All right. That's cool. So what kind of engineers or people are you looking for? Really right now, if you go use, if you go use vibes, you're totally allowed to roast it because I am a react developer, I guess, but I'm also a CEO and, um, it's like 75 % CEO code right now.

57:02So we've got a C level. Yeah. C level code. I like that. Uh, so if you're, if you're just like absolutely cracked and especially the person that the perfect hire is, you know, when somebody is kind of like new enough to a stack where they're like dangerously enthusiastic about getting everything right. Uh, if you're senior enough, you're going to see my flubs and be frustrated, but at the right part of your skills curve, you're going to just like chew up fixing that stuff and get it into best practices. Every, uh, level of CEO code is like an opportunity for the right person you know yep i just got like wordpress vibes in a way like in a positive way when i was looking at this golf friends thing i got built out here it's like kubrick like k2 was to to wordpress very every app has a certain style kind of thing to it i kind of feel like uh it's a good thing is there a shared is that on purpose chris is there a shared design aesthetic or something well we made the choice to differentiate ourselves from everybody else we're not using shad cn and that's not because it's not great we just want to be different we want to be more lightweight we want to have a little bit more variance and let clod or whoever express themselves a little more in there so the way we prompt the design language is actually uh my co-founder marcus i mentioned earlier just did a bunch of research like art history type research around like we don't want synthwave that's played out etc etc we found there was a design school in Italy in the 80s that they came up with a style they called Memphis and so we tell it to make Memphis we describe Memphis a little bit and it does a pretty good job of that that's all user editable so if you go into the settings page right now you can just type in your own style prompt you could switch it to synthwave you can switch it to synthwave and deep seek and then if you run it on deep seek now you probably have to generate the app 10 times before you get a working one but certainly a good playground for testing out these models and comparing them to each other probably better than my copy paste prompt into like four things is actually making probably better than simon willison's pelicans on bikes is like make the same app you know against all these different models that's cool i see the uh the style prompt now it's pretty cool you can just like swap that out make it make whatever you want it's your own Yeah.

59:23Right? Or if you really want to go deep, just hit up our GitHub, fork the whole thing, right? You know who you are and fix up my React. Like how much of this can you run? You know, how much of this is just completely, if I had enough gumption, I could get it running on my own Cloudflare account. So kind of, yes. What we have set up is even for if you're going in via the GitHub, it deploys to our endpoint and it uses our login system and that means that you could have projects. Basically, we want you to be able to be a Vibes DIY user, go run a fork. Maybe your fork is like internal for your work or something, but not have to do the whole heavy lift of the full stack.

1:00:05The fork will just run against our backend. If you want to get even heavier than that, yeah, now you can start to code up the backend, but that's a senior engineer task. How do you keep up with your underlying technologies in terms of what you're generating or what you're telling Claude to use? Because those things are also moving targets. I have more work to do there, right? There's models that aren't represented yet. I would love to get O3. I use O3 personally when I'm in WindSurf. And so, you know, there's some things we can do to keep up. We essentially need like a cultural ambassador to LOM land to keep us up.

1:00:41What about to Next.js land? Is that a fast enough moving target? I guess you're always generating a new one, so it doesn't matter so much. right and we're just doing that one file so i chose to do app.jsx instead of app.tsx mostly because it's one less thing the model can hallucinate wrong now if you wanted it to be txx i'm pretty sure windsurf can fix that for you in a single pass sure but why i guess by then you copy pasted it so it's yours anyways right do what you want exactly yeah the jsx is all about the simplicity and then the um it really allows anybody to get in there edit these apps and you know bring them to any back end when you do eject it runs through those same apis again you can move them over i don't know if there would be a good reason but there's a world in which you know especially when we spin up the user pays mode for like image gen ai usage by the app you might just pull our NPM modules directly into whatever environment and use those because that lets you ship apps without having to worry about the cost of the LLM.

1:01:50Say that again. I don't think I tracked it. So built into these NPM modules, it's part of our standard library is that when you run out of your free tokens, it pops up the login window. And after you log in and you get another batch of free tokens and run out of those, it asks for your credit card. If all you care about is going viral and the thing that's holding you back is that going viral is going to cost you$50 ,000 in chat GPT fees when people start using your prompts in production. Well do it on Vibes or do it with the Vibes NPM modules and you'll get the same benefit that will handle it for you and if you get enough usage then you could be looking at creator payouts.

1:02:33Yeah that actually scales really well i guess that's what you're referring back to the youtube model where you're basically as a app creator i'm bringing you token use by way of people using my app and you being vibes diy is making money off of every one of those people who decides to put down some cash in order to use the app some more and so you're now talking payouts to me for bringing you guys additional trap or additional customers that's that's an interesting model our real kind of eye on the prize, you know, couch did well, but I also learned firsthand what it's like to get whooped by MongoDB.

1:03:14At the time, you know, I wrote that, that rap about other no sequels, right? You can tell how it felt, but now I appreciate what they did, right? They understood that the real answer to taking the market is to be in on the ground floor when people are writing apps without permission in the enterprise and so we're you know probably a decent choice for say you're running a veterinarian clinic and your you know customer management system doesn't keep track of what the dog's favorite treats are um vibe up a treat tracker and you know uh on down the line the cryptographic causal consistency that's enforced by fireproof means that you know you could use this for regulated supply chain maybe your uh cannabis dispensary needs to keep track of some stuff because you know someone with a badge is going to come knocking and vibes has got the underlying infrastructure to make that safe.

1:04:20So after we make coding cool, we have a lot of bandwidth to go and make this system scale for serious use cases. Do you think your brand scales that way? You know, we'll find out, but I kind of think so. Here's a sub brand, Serious Vibes. Right. Totally. Yeah. We talk about gray mode. Gray mode. There you go. Yeah. There's a lot we can do there there's a whole like if you wanted to fork the core thing and make it work with say like not react like i got nothing against view i got nothing against solid js all these things are excellent technologies we chose react because it's the one that's going to give you the deepest training set but being able to take that uh the wrapper and deploy a view app or react app to our Cloudflare endpoint, it's not going to change things.

1:05:16From an infrastructure standpoint, it's ready to go. All right, dorks, get out there and fork away. For the normal people, get out there and remix somebody else's golf tea time tracker. Adams has already published it. And prove my vibes. My vibes were not so vibey. Get your friends into coding. get get some uh you know make uh an image generator that no one would have expected and make it go viral on your facebook i got a phrase for you ready for this i love vibe with friends vibe with friends that's right there you go and that's coming i mean that's just a easy on switch some of the folks we've been talking to are most excited about that this chat interface where you're talking to the llm and it's writing a code for you that's multi-user right as soon as we flip on the same sharing mechanism that you know allows adam to invite jared to the golf app you can also invite jared to be the coder on the golf app and y 'all can be in the chat together now you really are vibing with friends there you go awesome chris anything else that you expected us to ask you that we haven't asked you or that you can't wait to tell us about before we let you go y 'all did a great job i just can't wait to see what you vibe up i'm gonna vibe some stuff i'm gonna get my kids vibing this is gonna be fun vibes.diy if we haven't said it enough times on the pod that's your url vibes.diy there you go uh tell your friends get your kids get your nieces and nephews if you're of age similar to ours out there and do it yourself i mean i'm gonna throw a few things at this i think the image gen like the caricature stuff do you have a gallery of more like because sometimes one idea just strikes.

1:07:00You got to have something to start with and you're like, oh, I can just change that like the remix thing. Do you have a gallery out there? We moderate the stuff that shows up on the homepage. So we essentially have a carousel. Every time you hit refresh on the homepage, you'll get some new choices. There's some ones that illustrate how you do real things. If you have in your mind, as many of us, you know, dorks have a mental list of APIs that have cores and don't require an API key. I've got, you know, for instance, a vibe on there that is using Algolia's hacker news search to just bring you the vibe code news.

1:07:37So go remix that any API that's got that kind of access control, super easy to use. And then, as I said, with this backend support coming soon, you'll be able to drop your own API keys in. And what's the best way to get in touch with the creators of this yourself, your team, your community? Is there ways that you can say, Hey, I love support for this, that or the other thing and you guys don't have it yet, feedback or a Discord or a Zulip or anything. It's in the Discord and the Discord's linked from our About page. All right, go forth and vibe code with friends, especially once that multiplayer feature gets toggled on.

1:08:12Let us know, Chris, when that's out there because we'll definitely give it another shot. Probably another shout out as Adam and I could vibe code together. You know, I could be changing his design as he's trying to add features. That'd be fun. I'm looking forward to the day when your guests are on here with things they made in VybeZiY that'll be amazing that will be full circle won't it that's what I'm trying to talk about that's cool stuff that's the way it's got to be done I can't wait thanks Adam thanks Jared super excited to be here and yeah remember everything we do is open source so you're invited

1:08:49it was a fun journey into Chris's past and really cool to see how everything connects You know, it's really wild how someone like Chris Anderson, someone like him who can lead the way with Couchbase, CouchDB, all the NoSQL movement and the just what went on there. It was just a wild time to be a developer. It's always a wild time to be a developer, honestly. Fireproof is open source. You can check that out. And of course, vibes.diy. Get it on. Do what you got to do. Make something cool. Share it with somebody. Vibe it up, baby. Vibes.diy. Okay, friends, we're in Denver. Changelog.com slash live.

1:09:28Buy your ticket now. July is when it happens. Next month, you got a little bit of time, but do it now. Don't wait. Don't procrastinate. Super inexpensive ticket, 15 bucks. Come see Changelog IRL, a live show, a live launch, and all your fun favorite people will be there. me, Jared, Gerhard, Jason, Breakmaster, and some mystery guests. It's going to be fun. Meet up, live show, then a hike. It's the best. Again, changelog.com slash live. Of course, a big thank you to our friends over at Depot, depot.dev. Make your builds faster. That makes you faster. It is so cool. And of course, to our friends over at Retool, retool.com slash changelog.

1:10:16And our friends over at fly.io. We're big fans of Fly. You should check it out. If you're not on Fly, you are missing out. And of course, the Beat Freak in residence, Break Master Cylinder, bringing those beats every single week. Well, that's it. The show's done. We'll see you.

1:11:01Game on!

From the publisher

Chris Anderson joins the show. You may recognize Chris from the early days of CouchDB and Couchbase. Back when the world was just waking up to NoSQL, Chris was at the center of it all, shaping how developers think about data distribution and offline-first architecture.

These days, Chris is working on Vibes.diy and Fireproof — tools that make one-shot app generation not only possible, but shareable within minutes. We talk about the origins of CouchDB, the fork that led to Membase and Couchbase, and how that long journey led to this new paradigm: Vibe Coding.

More from The Changelog: Software Development, Open Source

All 232 episodes
When vibe coding goes viral (Interview)The Changelog: Software Development, Open Source · 1 h 11 min
Listen in VO