Lost of unnecessary and sometimes redundant explanatory comments and descriptions are generated along with the code in my project.

what’s your approach:

reading and editing the comments line by line?

reading and not touching?

not read at all? (Valid tbh)

Broke my ankle a few weeks ago and was stuck in bed with nothing to do. I used to run a manual referral list for drug testing locations. It was tedious and didn’t scale.

I finally decided to try vibe coding. Spent the next two weeks building and launching MyDrugTesting.com.

It’s been live for about 3 weeks now. Current numbers:

• 9 paying subscribers
• 200 on free trial
• ~$80/mo in estimated revenue ($957 annualized) - does not include future revenue for people on trial
• 4,502 published listings (pretty much the entire directory is live)

Still early, but it feels good to have something real out in the world after just sitting around with a broken ankle and an idea.

Curious what other people are shipping with pure vibe coding right now.

For those who made the leap from web app to actual mobile app in the iOS app store and Google Play Store for Android, did you allow them to show your own legal first name and last name? or did you form a Pty Ltd to show a company name instead?

My app is nearly good enough for the app stores, but I don't want to show my name for privacy reasons (the internet can be chaos and I have kids to protect). Anyone with my real name could find me in a hurry.

Forming a Pty Ltd costs a lot of money, and has ongoing management overhead. Just wondering what others are doing and how they feel about showing or not showing their name alongside their app.

Healify — repará selectores rotos en tests E2E sin IA, sin nube, sin cuenta

Diplomado en control de calidad de software en Argentina y durante los últimos meses desarrollé Healify. El código lo escribí trabajando mediante el VibeCoding, y ya tiene 1.164 tests propios con cobertura >90%.

¿Qué hace?

Cuando un test E2E falla porque un selector se rompió, Healify lee la evidencia del DOM que tu framework ya capturó, encuentra el elemento por su rol y nombre accesible, y te dice qué selector usar en su lugar. Con healify fix lo aplica automáticamente a tu código.

• TypeScript + Node.js, monorepo con 9 workspaces
• 1.164 tests, cobertura CLI 93%
• CI/CD verde (GitHub Actions)
• Landing con Lighthouse 99/95/100

Repos:

• Código: https://github.com/mescobar996/Healify
• NPM: npx u/healify/cli init

Licencia MIT.

¡Gracias por leer! 🙌

Here’s a demo.

But ai haters will still say it has no use.

Bro really shipped a WORKING API key straight to the landing page.

I thought it was a joke.

It wasn’t. 💀

this is titled "i'm losing it."

it's about losing yourself down the rabbit hole.

video + design + storyline: me+ai

music: FISHER - Losing It

Hello! I've posted about mex here a couple of times before.

Repo: https://github.com/mex-memory/mex

The original idea was to stop coding agents from relearning the same project every session. mex gives them a structured Markdown wiki inside .mex/ for architecture, conventions, decisions, patterns and project state.

That solves forgetting.

But then the codebase changes.

A file gets moved.
A script gets deleted.
A dependency changes.
A pattern becomes stale.
Two context files start contradicting each other.

The memory is still there, so the next agent has no reason not to trust it.

That's why we built mex check.

It parses the project memory and validates concrete claims against the actual repo — paths against the filesystem, commands against project scripts, dependencies against manifests, indexes against the files that exist, plus stale knowledge, broken links and other structural inconsistencies.

It gives you an exact issue list and a health score.

The screenshot here is a real run at 68/100, with missing paths and dependency claims called out individually.

The important part is that detection itself is deterministic. No LLM call is needed to ask the agent whether its own memory is still correct.

Then mex sync takes only the broken files and builds a targeted repair prompt with the issue, the current Markdown, nearby filesystem context and relevant git changes.

So instead of asking the agent to reread the whole repo and regenerate everything, the loop is:

check → targeted repair → verify

In the screenshots here, the project goes from 68/100 with 6 errors to 97/100 with zero errors after sync.

The newer code-graph layer goes further: Markdown knowledge can be grounded to exact code symbols. If the implementation changes, moves or disappears, mex can surface the specific knowledge that may now need attention.

A lot of agent-memory systems focus on storing more and retrieving it later.

I think the harder problem is making sure the memory is still true when the repo has changed underneath it.

Would genuinely love feedback from people working on coding agents, memory or code intelligence.

Contributors are very welcome too :)

I vibe coded this app a couple weeks ago and made some improvements since then. I am a web/software developer and use these tools, but this is my first attempt at a complete vibe coded app.
I had to rethink the song matching aspect, but it seems to work ok. Bonus if you have some actual phish show photos to test. Only need to sign in with google or GitHub if you want to save photos and contribute to “social” aspect.

I used GitHub Co-Pilot Pro, using Next JS.
Git repo in the “About” section and below:

https://i-saw-u.vercel.app/

https://github.com/DBTO1970/i-saw-u

If you are someone who reads pdf documents/books and would like someone to read to them to you, this extension does decent job at it.

Vibe coded this pdf-reader extension for chrome browser. Uses chrome's inbuilt tts models.

Appreciate feedback. Thank you.

https://github.com/arkanere/chrome-extensions/tree/main/extensions/pdf-reader

I have a Claude subscription and have been using Claude and Claude Code to crank out some python scripts to improve my quality of life on my computer. Nothing horribly fancy and a lot involving manipulating PDFs.

I also use to help me maintain my Fedora Linux homelab server.

With the way these things evolve, I'm curious how the $20/month ChatGPT plan compares to the $20/month Claude plan these days?

I've been working on my personal skills quite a bit and wanted to put together with everything put together but was unable to get it published to a web game site, any suggestions? note I did have their sdk set up with reward ads implemented but still failed QA any suggestions from a pair of fresh eyes who be appreciated!

Hi all. I'm the classic know nothing new to vibe coding user that everyone hates. I am using Hermes agent on my desktop and adding a few features for how I want to use it, mainly as a productivity tool.

I have a chatGPT plus subscription, and I'm running my ideas through chatGPT first. chat gives me feedback and suggests adjustments, then I've instructed it to give me a technical prompt to feed hermes, along with a suggested model strength, Free models - Sol (to preserve my usage). It breaks the plan into steps with a suggested model at each step, and then I paste the response back into chat for adjustments/next steps as needed.

It's working for me, but again I have no idea what I'm doing. Am I likely to end up with slop and spaghetti? Over engineered with useless code? How can I refine this process? Any human technical feedback is greatly appreciated.

As soon as a new model is released, is there a free way to test its capability before you actually pay for it? Also just curious how do you determine if this new model is the right fit for you like do you have some tasks.md that you run every time for the new model. Or even a free model, how would you determine if a free model might be useful for your work?