Hey everyone

No CS background. Started vibe coding 3 months ago.

16+ hours daily. 15 billion tokens later I'm still learning.

I was using a Claude Code leaderboard service made by another dev.
Submitting my daily stats became my end-of-day ritual. It was my fuel for vibe coding.

The funny thing about building an AI product right now is that the hard part keeps changing.

A couple years ago, I was obsessed with offline evals. They felt clean. You write a test, you run it every time you change something, and you get a number you can trust. If the number goes up, you ship. If it goes down, you fix it. It s the kind of engineering loop that makes you feel like you re in control.

Every vibe-coding session starts the same:

Here s the context again
Here s what I already tried
Please don t repeat this

That friction killed my flow, so I built Blocpad (CLI).

It keeps context with the project, not trapped in chat history tasks, decisions, notes, all local.
AI reads the state. No re-prompting.

Everyone went crazy in 2025 after AI Memory. There are atleast a dozen launches in the space on product hunt from june-december, but the problem seems far from solved.
Are you using any of the current memory systems (platform specific or interoperable ones, doesn't matter).
What do you still hate in these systems? is it context repetition? is it hallucinations? is it inability to move between systems with your memory intact?
Want to wrap up the year knowing what people actually need!

Hey everyone, been a Product Hunt visitor for years but never signed up, so I thought I'd start by sharing some recent learnings that hopefully other builders will find useful.

For context, we're building FanBase Copilot, an AI assistant for content creators that learns their voice and context over time. The memory layer is critical. It's what makes the AI actually useful after the first conversation.

Our team pushes code constantly - multiple deploys per hour some days. The problem? Nobody can keep up with what's changing. You check the repo in the morning, grab coffee, come back and suddenly there are 47 new commits.

Good luck understanding what actually matters or how it affects your work. We built Doculearn to solve this with automated flashcards. Here's how it works:

This was a deliberate experiment inspired by my CTO. I wanted to test a simple question:
Can a Product Manager ship a real website end-to-end today without handoffs?

Here s the stack:

• @Figma structure, hierarchy, & visual components

• @Adobe Illustrator brand consistency & visual components

• @ChatGPT by OpenAI positioning, copy angles, objections

• @Lovable iterate layouts before committing

• @Cursor turn ideas into real UI fast

Building my app with AI tools, zero coding background. The magic part - I can ship features in hours. The scary part - I have no idea if the code is actually good.

Right now my "QA process" is:

- Does it work when I tap around?

- Did anything break that worked before?

Reddit has been my main growth channel for the past 6 months and I've been consistently getting 100+ high-intent visitors every week.

Here's the exact system you can copy:

See this?

Step 150 of debugging why a payment does not get saved to a database. Two days on this one bug. And there are plenty more. If you can build somehing that will do the back-and-forth, the "now try this and tell if it... no? Okay, le's do this thn, and this, and that..." Do what Claude Opus 4.5 is tellling me to do, the tens of hours, to get to the solution. Automate that and you have a winer - becuase there are 100K full-stack devs who will do all this more effienctly themselves, yes. but there are 10M non-developers who love what they built, but are getting killed in the debugging, the last 5%.

Digg is back.

The onetime news aggregator relaunched Wednesday as a Reddit competitor, with founder Kevin Rose and Reddit co-founder Alexis Ohanian at the helm.

AI and no-code tools are evolving insanely fast right now. Every few weeks there s a new tool that changes how quickly you can go from idea to product.

I ve been experimenting a lot with different vibe coding platforms lately, trying to find the right balance between speed, control, and flexibility. What s surprised me most is how far you can go today without a traditional engineering setup.

For context, I recently built @Sendrise , an all-in-one cold email outreach platform, using a no-code + AI stack. I used @Lovable for building the product flows and UI, combined with AI tools for writing, automation, and logic. What started as an MVP quickly turned into a fully working product with lead management, campaigns, CRM, and analytics.

I have been cranking out apps for the past few years and loving it.  Then one morning a week or 2 ago I got a little ambitious and decided to build a desktop email client because outlook was so-so and superhuman was ridiculously expensive.  

Is this a big mistake?   Am I wasting my time ?

I've been vibe coding( @Lovable , @v0 by Vercel ) for a couple of months now & it's such an incredible feeling. What once required specialized skills now happens through simple descriptions.

Breaking free from dependency on designers & engineers for mocks/prototypes has been especially empowering. Great to see this creative autonomy that has fundamentally changed how people build.

What an incredible future we are creating for kids who can create software from sentences.