This is an interesting idea! I've found that the valley between customers and being able to work directly with a helper like you describe is too vast for meaningful interaction to work.
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.
I'm also only a sample size of one, but I previously offered web development in a similar fashion (pre-LLM) and I found that clients didn't have the working knowledge to even know what they wanted to guide or influence the project in any meaningful way.
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.
>I'm also only a sample size of one, but I previously offered web development in a similar fashion (pre-LLM) and I found that clients didn't have the working knowledge to even know what they wanted to guide or influence the project in any meaningful way.
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...
This is an interesting idea! I've found that the valley between customers and being able to work directly with a helper like you describe is too vast for meaningful interaction to work.
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?
Thanks!
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.
I'm also only a sample size of one, but I previously offered web development in a similar fashion (pre-LLM) and I found that clients didn't have the working knowledge to even know what they wanted to guide or influence the project in any meaningful way.
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.
>I'm also only a sample size of one, but I previously offered web development in a similar fashion (pre-LLM) and I found that clients didn't have the working knowledge to even know what they wanted to guide or influence the project in any meaningful way.
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...