Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

yeah, bogus... proper time keeping is key to being a contractor. If you are going to work multiple (which happens when you're brought on as an expert but there's spirts of work between lapses of down time) then you can't be doing one while on the clock for the other. Wage theft.


Not necessarily. It depends on the requirement. If I've completed or don't have any real work, but am expected to be around, then that's work. It's only if the second contract breaches the first or creates a conflict, and that's not inherent in time.

Edit: Misread your comment. If you're billing for specific and granular blocks of time, and doubling that up, then ya wage theft. But if you're doing that and also expected to be onsite anyway, then no not wage theft imo.


If you're a company and you see github commits through firewall, why take the chance unless he's really really good?


You wouldn't, I was saying that there could be situations where it wouldn't be a valid claim for wage theft. I would say that's also true of regular jobs where you're not necessarily even expected to be there all the time. I've made commits from my desk on side contracts, but if there's a conflict, I resolve it by sticking around longer. If my employer or client has a problem with me working on other shit, then they get to stop being my employer or client




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

Search: