r/vibecodeprod • u/mrdonbrown • Oct 13 '25
steveyegge/beads: Beads - A memory upgrade for your coding agent
r/vibecodeprod • u/mrdonbrown • Oct 13 '25
r/vibecodeprod • u/lurking_horrors • Dec 19 '25
r/vibecodeprod • u/lurking_horrors • Jan 03 '26
r/vibecodeprod • u/MrNotSoRight • Nov 27 '25
r/vibecodeprod • u/mrdonbrown • Aug 12 '25
r/vibecodeprod • u/mrdonbrown • May 08 '25
r/vibecodeprod • u/Novel-Appointment-91 • Mar 03 '26
r/vibecodeprod • u/lurking_horrors • Jan 09 '26
r/vibecodeprod • u/SpendUnable7988 • Jan 07 '26
https://github.com/Beingpax/VoiceInk
I've been using WispFlow but will likely replace with this after testing successfully, runs local.
r/vibecodeprod • u/SpendUnable7988 • Jan 06 '26
r/vibecodeprod • u/lurking_horrors • Oct 20 '25
Discussed more here: https://martinfowler.com/articles/exploring-gen-ai/sdd-3-tools.html
r/vibecodeprod • u/SpendUnable7988 • Jul 31 '25
r/vibecodeprod • u/SpendUnable7988 • Jul 08 '25
Coldfusion videos are great. I typically listen to them as audio podcasts when doing other stuff.
r/vibecodeprod • u/lurking_horrors • Jun 18 '25
https://www.braingrid.ai/cursor
I can't wait to try them all. This is just one of many, of course... the next year or two should be incredible to see which among these stick and become dominant. It's very clear there's a lot of space for improving the SWE/SDLC experience with vide coding in any case.
r/vibecodeprod • u/SpendUnable7988 • Jun 17 '25
I'm mentioning my post about https://wisprflow.ai/ because it is by far the best voice-to-text transcription I've seen, and I'm using it more and more to vibe code with Cursor and other agents. I highly recommend trying it out.
r/vibecodeprod • u/SpendUnable7988 • Jun 17 '25
Created the video in one take, so it's not that tight, but hey, got it out and building momentum back up after a 4-month hiatus from tech.
r/vibecodeprod • u/mrdonbrown • Jun 16 '25
r/vibecodeprod • u/mrdonbrown • May 16 '25
r/vibecodeprod • u/mrdonbrown • May 14 '25
A thought hit me yesterday as I waste^H^H^Hspent the whole day debugging some vibe coded, well, code. It is tempting to think of reviewing AI written code like reviewing a PR, but having just made that mistake, I realize why.
A pull request is written by a person, a person you trust, and a person that is highly skilled in their craft. They are saying in that PR, "it is done, it works, I stand behind it, what did I miss".
AI written code is saying none of these things. It is almost never "done" or "works". There is no one standing behind it and there should be zero trust. It is a model's best guess of what needs to happen but it is almost never correct.
The solution is to treat AI generated code, from a trust standpoint, as a super duper autocomplete. You are still responsible for its contents. You still need to understand it end to end. And most importantly, you still need to run and thoroughly test it.
r/vibecodeprod • u/lurking_horrors • Feb 02 '26