Hacker News Reader

One person's "bad codebase" is another contractor's windfall project.

We collect end-of-project feedback from both sides, so hypothetically a difficult client would eventually be surfaced in the same way as a bad contractor.

We also try to keep tasks small. I think that a 10 hour task lets both sides test working together (and get paid in the process), and if things work out well - then they can continue working on tasks.

Like protect them how? If you reject every company with a 'bad code base' you will be left with a very small pool of companies. Depending on how you define that.