Hacker News Reader

Fully agree. Om this note, I had a brief discussion with an employer I collaborated with once, about some potential employees being forced to work in the open because they open sourced their work. I was terribly surprised to get no understanding that this could be perceived as a problem. Especially since work tasks may not be something you would want on your public record necessarily.

View on HN

In this case, I would recommend that you get an employer-specific GitHub account, so you can compartmentalize it that way. A bit of a hassle, yes, but then, you're definitely not tying yourself in git history to that employer for your entire career.

Can't find it now but I faintly remember this being against their ToS, maybe even before the Microsoft days.

Docs say that it's no problem now, but they "suggest merging multiple accounts" but probably because of less fuckups and support questions.

That's interesting. I wouldn't be surprised. Thank you.

That's of course a good solution. Thank you.

Reply on news.ycombinator.com