Hacker News new | past | comments | ask | show | jobs | submit login

I like the aspiration to grow engineers — it’s a laudable, and worthy, goal.

But I also feel there is a little bit of a pandora’s box here.

The model you’re creating here is more structured ‘gig economy’ path for software dev. Sure, you’ve got things like UpWork, and other freelance products, but the purchasers (e.g., business) are effectively taking a risky bet on the work which can tamper commitment to purchasing work that way.

But with ‘no merge, no fee’ could create a very strange dynamic where companies will opportunistically throw work over the wall and create bounty-like dynamics. I don’t know if this is particularly bad for the purchaser, but for the seller that could lead to some challenges overtime (race to the bottom etc)




No merge no fee was really there to guarantee quality and bootstrap trust. We take the hit and pay the devs either way.

If it is abused we would take action to intervene but hasn’t happened yet. When it does happen (< 5%), it’s really good learning feedback for devs

But would you reckon there is another way to solve the power imbalance problem?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: