3 ms·
One of the first things I do upon joining a new company is use the new company email address to register a github account, assuming there isn't an enterprise Gi
by xnorswap 5y ago
One of the first things I do upon joining a new company is use the new company email address to register a github account, assuming there isn't an enterprise Github and it's allowed as part of policy. ( I also register a new HN account, it just keeps things cleaner although I want to be clear this is still a personal account and doesn't represent work. )
Work and home emails / github / phones / everything are separate, I wouldn't want to ever mix them.
Yes, that means losing some history when changing employers, but that's part of the deal. You work for your employer and while they are tolerant (to various degrees) of engaging with open source, in return they get to retain ownership of that email address and their brand.
In a new company I have a new "hat" on, and while I can see and interact with my previous issues, I'm no longer that person with a new hat on and can only indirectly interact with my other self as if a different person.
- zxspectrum1982 5y agoSame here. Last thing I want when I move to a new job, especially if moving to a competitor, is have people ask me to fix bugs/answer their questions about my old code, which would be creating a conflict of interest.
- move-on-by 5y agoI keep work and personal accounts separate as well. I do a fair amount of open source work and maybe one day I will find a way to generate some passive income. If that day ever comes, I want there to be a clear separation between work done for my employer and work done for myself. It is important to maintain a clear separation between the two.