I've been thinking about something. We've gotten really good at using AI to generate working code, but we're not treating it like production code in terms of documentation.
Traditional developers spend significant time documenting their code because they know future them (or their teammates) will need to understand, modify, or debug it later. But with AI-generated code, we often just copy-paste and move on.
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.
Background: We have built an AI assistant (Tasker) that can do all sorts of tasks on your behalf.. from using a browser to doing deep research to connecting to your GSuite and all your SaaS apps etc.
I've recently implemented a coding tool for Tasker to use. I asked it to create a website with a Google Sheet as a database, and it worked surprisingly well.
I then started asking Tasker to take on different roles to run my website based on triggers:
I ve been building a product that involves a mix of AI-driven matching + dynamic user experiences (can t share exact details yet). The idea is to create something that feels alive and adapts to each user s vibe.
But here s my dilemma I m torn between focusing first on core UX feel (smooth, immersive flow) or AI logic depth (smarter matching + personalization).
For those who ve shipped vibe-heavy or AI-integrated products what worked better for you early on?
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.
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?
Taskade started as a real-time collaboration tool for planning and productivity. Then we added memory, agents, and automations. Soon it stopped feeling like a static tool and started acting like a real living workspace that could handle parts of the work on its own.
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.
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%.
