keeping the side project off the work laptop when lunch is the only free hour
Day job laptop is managed, work GitHub is behind company SSO, and realistically my best clear hour is between 12 and 1 sitting at my desk. Evenings are two tired hours after the kid goes down.
I want a setup where there is no argument later about what was built where. Not because I think anyone is looking, but because I have read the employment agreement twice now and it is vague in the way those things always are.
So, practically: how do you keep two identities apart day to day? Separate machine, separate git config, separate everything? And what do you do about the fact that the only real focus block I get is on their premises during their hours.
@chain_wear_chase · 4w ago · 3 replies
Split it at the hardware line and stop trying to be clever below that.
The config tricks are real and worth doing on your own machine: an includeIf on gitdir so anything under ~/side commits with the personal email automatically, a separate ssh key with its own Host alias in ~/.ssh/config, and a browser profile that has never seen a work login. That prevents the honest mistake where you push at 11pm with your work email in the author field.
But none of that helps if the bytes ever touched their laptop. Own machine, own network, own accounts, own hours. That is the whole argument, and every extra layer under it is decoration.
Reply
Report
@supa_okonkwo · 4w ago
Worth spelling out for anyone reading who has not thought about it: a managed device can generally see far more than people assume, including browsing in a separate profile and in private windows, because the management stack sits below the browser. Same for a personal phone that is enrolled for work mail. Private mode is a privacy feature against other humans using the same machine, not against the people who administer it.
Reply
Report
@epsilon_eddie · 4w ago
The includeIf thing fixed a real problem for me. I had four months of commits authored with my work address, which looked terrible and was purely a misconfiguration. Two lines in ~/.gitconfig and it has never happened again.
Reply
Report