Show HN: Vibeplace.ai hire a human in the loop for vibe coded projects
After a year of skepticism, I finally tried LLM-assisted coding, and I'm genuinely impressed! I can now spin up multiple instances of Xcode and VSCode and churn out code at a speed I never thought possible. Yes, the majority of the time the code needs significant refinement and guidance, often feeling like I'm dealing with an unmotivated teen. However, with enough focused prompting, it can produce decent results.
This prompt-review-merge loop, however, has made me the bottleneck in my own workflow. I wish I could outsource basic PR reviews to truly scale this process.
I also see a "gold rush" among non-engineers using LLMs for "vibe coding." While they're excited, they often overlook critical aspects like exposed API keys, SQL injection vulnerabilities, and ballooning cloud costs. They clearly need professional engineering oversight.
It became clear there's a missing piece for both scenarios: a human in the loop.
So, I decided to build a solution to bridge this gap and meet the demand for specialized support during this LLM-powered gold rush. I created vibeplace.ai.
vibeplace.ai is a double-sided marketplace connecting "vibe coders" with experienced professional engineers. Whether you're looking to take an idea from zero to one, scale from one to N, or simply resolve a technical bottleneck like my own, vibeplace.ai provides the expertise you need.
Do you see yourself on either side of this marketplace?
Vitalik
If the customer is paying enough, it can be worth it. But it would take a decent developer to be the helper in this situation, and that developer could likely make more money doing other work, so it makes it hard to grow this model in my mind. What are your thoughts on attracting talent to the provider side?
I think you are absolutely right. A mediocre engineer will not fit this marketplace, since LLM already produced a mediocre code by definition.
As for talent. Honestly, as an engineer, I would be attracted to success and a challenge. Say someone vibe-coded a successful product and struggling to scale it up. That is a message I'm approaching engineers right now. But I fully understand that I'm a sample one and open to any other views.
Perhaps your audience would be able to work with the dev/LLM in a more harmonious way -- I found that both the developer and customer became frustrated with the experience and most projects reverted to a "here's a draft, let me know what you want changed" flow to satisfy the deadlines. Don't let me deter you, I'm just sharing what derailed me in a different but similar adventure.
Well, I can definitely see it! People jumping onto the vibe-coding bandwagon as if there are no risks. I think at some point the users will build enough pushback so the vibe coders start looking for engineers to at least prevent a huge flop.
> Perhaps your audience would be able to work with the dev/LLM in a more harmonious way -- I found that both the developer and customer became frustrated with the experience and most projects reverted to a "here's a draft, let me know what you want changed" flow to satisfy the deadlines. Don't let me deter you, I'm just sharing what derailed me in a different but similar adventure.
Absolutely! I'm not a stranger to Upwork/getafreelancer on both engineer and customer side. The most crazy projects were when people built something from sticks and stones claming that they've done 80% and now need to finish 20%. When in reality it was a good case for a complete rewrite. Here is an avid example: https://www.reddit.com/r/vibecoding/comments/1l46lh1/i_tried...