News for hackers. Stuff that matters.

ufvy

Chefs.Video/earn
OP here. A few technical details on the video implementation if anyone is interested:

We are using Simulcast for the video tracks. Since a 'Chef' (Buyer) might have 5 freelancers in a room sharing screens simultaneously, bandwidth was a massive bottleneck in early testing.

We configured the LiveKit room to dynamically downgrade the video resolution of the 4 'passive' screens while keeping the 'active' focused screen in 1080p.

Also, regarding the 'surveillance' aspect: I know this is controversial. The goal isn't to watch someone work for 8 hours a day. It's designed for 15-30 minute sprints to verify skill before offering a longer contract. Think of it like a pair-programming interview, but paid.

Show HN: Chefs.Video – A marketplace where you pay freelancers $0.005/second

https://chefs.video

Hello HN,I’m the solo developer behind Chefs.Video. It’s a platform for hiring freelancers (devs, designers, editors) by watching them work live, rather than relying on portfolios or resumes.The Problem: I got burned hiring a React developer on Fiverr. He had 5-star reviews and a great portfolio. It took 2 weeks and $300 to realize he was outsourcing the work and pasting bad jQuery code....

( Read More... | 1 comment | on HN )
Now with 20 dollars of free credits
Now with 20 dollars of free credits
Now with 20 dollars of free credits
We give $20 of free credits, try it at Gigs.Quest/hire
At the moment, I need more founders to create rooms.
Thanks
1.2 dollars per minute is pretty cheap.
Really appreciate this thoughtful feedback! You've identified some key improvements:

*Variable rates*: Love this idea. Right now it's flat $72/hr, but you're right – a junior dev shouldn't charge the same as a senior architect. Thinking through implementation:

Option A: Participants set their own rate ($30-$200/hr range?) - Pro: Market finds equilibrium - Con: Chefs don't know cost upfront (pre-auth becomes tricky)

Option B: Skill tiers (Junior $45/hr, Mid $72/hr, Senior $120/hr) - Pro: Predictable pricing for chefs - Con: Who decides the tier?

Leaning toward Option A with a visible rate display before participants join. What do you think?

*Quality & reputation*: Totally agree – even Google/Meta make bad hires sometimes. Your "let it sort itself out" approach makes sense. I'm thinking:

- Public profile showing: total earnings, # sessions, avg session length - No ratings initially (avoids gaming/fake reviews) - Let the market decide: if someone consistently gets kicked or has 2-min sessions, that's a signal

The earnings transparency might be enough – someone with $10k earned across 200 sessions is probably legit.

*Room matching with AI*: This is brilliant and solves the discovery problem elegantly. Currently participants just see a list of open rooms. Your idea:

1. Freelancer creates profile: "React expert, 5 yrs exp, good at performance optimization" 2. Chef creates room: "Need help with Redux state management causing re-renders" 3. AI matches and notifies relevant freelancers: "New room matches your skills"

This could use semantic search (embeddings) to match "Redux performance" to "state management optimization" even if terms don't overlap exactly.

Quick prototype question: Should I prioritize variable rates or AI matching first? Which would have more immediate impact?

Thanks again – this is exactly the kind of feedback I need.

Ask me anything. My first launch

Show HN: Real-time freelancer marketplace with per-second billing

https://gigs.quest/

Hi HN! I'm launching Gigs.Quest, a platform where startups can hire freelancers instantly through live video rooms.Problem: Traditional freelancing platforms are slow. You post a job, wait for proposals, interview candidates, negotiate rates, then finally start work. For quick tasks, this is overkill.Solution: Create a room, describe what you need, and qualified talent joins live within...

( Read More... | 14 comments | 2 points | on HN )
Re:The Railsification of SaaS on Tuesday March 09, 2021 @08:11PM (#26406608)
Unfortunately Autocode doesn’t use graphql