Hacker News new | ask | show | jobs
by itake 825 days ago
Setting up the env probably eats into your margins.

Whenever I onboard a new contractor, they bill me 4+ hours just to get the thing to run on their machine and understanding the code base.

I'm curious if you're constantly having different devs, this overhead for each dev makes it less appealing on both sides of the table.

I also had someone (who I gave paid trial "tiny task") steal my codebase and post the code publicly on github to pretend to use in job interviews. Ever since then, I try to minimize the number of contractors I allow access to my source code.

How do you prevent the subcontractors from doing this?

1 comments

True, any new task even though how tiny it might be, needs few hours to understand and get the local environment up. The onboarding of a new client requires some effort even if the same devs remain the same. So in the long run it comes down to niching down to specific workflows which are profitable and which is nothing but PMF. Given, most of the devs who I work with are from my network, the real challenge of confidentiality issues are a bit too early now. But at some point an NDA and his recent work ratings are some factors which could help in avoiding those issues. But again nothing is foolproof.

But stealing the codebase is going too far.