Replies (19)

This is a great review of vibe-coding! I’ve come to the same conclusions after 3 months of doing it, except I didn’t know about the Stacks thing. I’ll check it out for next time! View quoted note →
Very cool, thank you. Our job is to provide the impetus to start, serve as guides on the way, and ultimately enjoy the result. In a way, there is no point for AI agents to do anything at all. Rationally, it is all hopeless anyway. It is the many brilliant human illusions in the first place that make it worthwhile to create and try new stuff.
This is a fantastic article on the ins and outs of vibe coding. I've used Stacks with 2 out of 3 applications that I've created. Stacks and the MKStack for Nostr applications makes vibe coding incredibly easy to go from idea to usable application. If you've asked me what I've learned or what I've been doing or how I've done it, this article explains it all. Well done @MK Fain 🤙🏻🫂💜 Happy vibing!
Soapbox's avatar Soapbox
Thanks to the help of #AI tools, the @And Other Stuff team built Chorus in less than a week. Here's how you can replicate the process and launch your own #Nostr client in days:
View quoted note →
“When vibe coding, the human’s role is not to write the code or to even care about the code. The role of the human is to be the visionary that imagines the end goal of the product, and prompts it into existence.” @MK Fain nailed it. View quoted note →
Besides being vibecoded into existence... what's so special about this client? Why should I try it - what's the value proposition and how do you intend to maintain it if lots of bugs appear?
Great questions! Public and private groups on Nostr have been a major pain-point with many disparate implementations, none of which seem to fully meet the needs of users or provide a genuine alternative to Facebook groups. Solving that was the main goal of this project. While I focused mostly on the process of creating Chorus in this post, I'd love to do another deep-dive into the implementation we chose and why, how we expanded NIP-72, and the future plans to improve and grow it. In the short term, I can tell you that the @And Other Stuff team definitely has plans to keep working on this client! I recommend checking out the "Future" tag on Github for a list of the things we already know we want to do, and we welcome bug reports as well!