Trying to make sense of "vibe coding" with VibeCodingHub
3 comments
Love this. I know that the view on vibe coding is pretty scattered online. Personally i got into this type of coding about 3-4 months ago. My background is 6 years in university becoming an engineer, where my master was aimed towards people in projects, organizational structures and management. I combined these studies with a couple of programming and DB courses. I feel that due to "vibe coding tools" i can adopt a project management approach to my fleet of coding agents. I draft plans, development phases and so much more. I can add that i am nowhere near a professional software engineer. I can say that where these tools are today, they require this type of management.
All these coders trying to tell the AIs what to do when they have the "design picture" already in their head's become frustrated cus the Agent can't read their minds and dig into their intuitive ideas developed from years of coding experience.
I don't say that this is "the way" but rather an approach to AI-coding that has worked for me. With little to no coding experience, i have managed my coding agents in a way that they have build a saleable and pretty complex solution for me, that will kickstart my business this summer. I have professional software engineer friends that have revied it and they are amazed of the quality of the code.
All these coders trying to tell the AIs what to do when they have the "design picture" already in their head's become frustrated cus the Agent can't read their minds and dig into their intuitive ideas developed from years of coding experience.
I don't say that this is "the way" but rather an approach to AI-coding that has worked for me. With little to no coding experience, i have managed my coding agents in a way that they have build a saleable and pretty complex solution for me, that will kickstart my business this summer. I have professional software engineer friends that have revied it and they are amazed of the quality of the code.
Like many of you, I've seen the term "vibe coding" floating around – using LLMs via natural language prompts to generate code, sometimes without deep scrutiny (popularized by Karpathy, seen in tools like Cursor). The discussions are all over the place: excitement about accessibility, fear of technical debt, debates about its viability.
It felt like the information was scattered. So, I built VibeCodingHub ( https://vibecodinghub.borninsea.com ) as an attempt to consolidate resources and foster clearer discussion.
The site brings together: 1. *Definitions & Context:* What is it, really? Pros/Cons? 2. *Tool Directory/Reviews:* Focus on tools like Cursor, Claude, Replit commonly used for this. 3. *Prompt Library:* Sharing working prompts for common tasks. 4. *Community Space:* For sharing projects and discussions (early stages). 5. *News Aggregation:* Tracking the trend.
The goal isn't necessarily to promote vibe coding, but to provide a central resource for understanding it, finding relevant tools/techniques, and discussing it critically.
Launched this recently and looking for feedback from the HN crowd: * Does this fill a gap you've noticed? * What's missing? * Is the balance between hype/potential and risks/criticism right? * Any usability issues jump out?
Appreciate any thoughts or suggestions!