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.
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.
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.
I just launched AllPub.co and built pretty much the entire thing using Vibecoding with Claude Sonnet 3.5. I'm a software architect with just some basic Python knowledge, so this was my first full web app build. Wanted to share my experience!
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.
Netflix for AI generated fims, pretty self explanatory
Problem
This week, Google unveiled Veo 3, its latest AI video model capable of generating hyper-realistic videos from text prompts. The line between AI-generated and human-made content is blurring rapidly.
As devs, we all know the struggle with code security scanners:
Switching between IDE and clunky dashboards to check vulnerabilities
Wasting hours sifting through false positives
Getting vulnerability alerts with zero guidance on how to actually fix them
I stumbled on an IDE extension (ZAST Express for VS Code/Cursor) last week that s amazing for my workflow. The Proof of Concept (PoC) feature is what sold me instead of just flagging issues, it gives runnable snippets to validate the problem, plus clear fixes right in my editor. No context switching, no guesswork, and it s free to start.
Are you someone who's built > 10 apps using Lovable, Replit, Mocha, or another vibe coding tool? If so I'm very interested in what is your answer to these 2 questions:
Assume you're the "benevolent dictator" of one of these apps for the day, and can choose to add one thing, and remove one thing:
What's your most desired feature? Thing holding you back the most?
What really annoys you and would you change or remove?
Vibecoding matters because it encourages coders to think outside the box. It challenges the norm of purely functional, cookie-cutter websites and apps. It's about bringing soul to the screen and taking digital experiences beyond utility, creating something that resonates with users on a deeper level.
