3 ms·
I didn’t read it as “significantly” affect work performance at all, it seemed more like it anything that DOES affect work performance is a problem EDIT: Also i
by granshaw 3y ago
I didn’t read it as “significantly” affect work performance at all, it seemed more like it anything that DOES affect work performance is a problem
EDIT: Also it seems like they don’t like you doing things similar to what they paid you to do, even if it’s not in competition at all… so sounds like after hours coding consulting even in a complete different industry would be frowned upon even if it didn’t affect your performance
So all in all, still pretty strict
- ghaff 3y agoI think that's pretty normal conflict of interest language. Seems pretty reasonable in general. You do see broader permissions around things like developing open source software at some companies but they're not common.
- granshaw 3y agoYes my point was more "this policy is nothing special or more lenient than the usual"
- ghaff 3y agoAt least as a practical matter. Some large companies (in particular) may have draconian policies about doing moonlighting but it's probably not a big deal generally as long as it's low-visibility.
- granshaw 3y agoIn all cases, you'll want to keep it to yourself, is my advice :)
- ghaff 3y agoOh. I agree. I avoid obvious conflicts of interest. And for any unpaid and pizza-paid advice/minor work for people I do it quietly. But that stuff is pretty simple relative to a (minor) real side-gig which I had (shareware back in the day) but was pretty much orthogonal to my day job and my manager knew about.