At work, I have been doing a number of activities that are probably seen as suspicious or bad. I need to fix these, or at least minimize their visibility:
- I update my Github code from work
Although these are primarily ~/.*rc files and tiny (~100 line) Perl utils, they could still be construed as copyright violations by my employer. Writing code while on the clock means that the employer owns that code. Generally, uploading code to public websites from within a large corporate workplace is a huge red flag — it's the sort of activity that people interested in corporate espianage do.
- Updating my website while at work requires SSH access
It's unlikely that an employer would claim copyright over employee's personal blog postings. However, SSH access to external computers is often prohibited or at the least very difficult (at large corporations anyway).
The first question for each is: Do I really need to keep doing these? Obviously, if my employer doesn't want me to do these, I shouldn't.
My people's personal websites don't require SSH access to update. Most employers are okay with employees updating personal blogs, etc. Here, it's the method that's the problem, not the content itself.
- Git repos
well, uh, ...
In some ways, what I'm doing isn't far off from Firefox Sync — I'm synchronizing my system settings.
In other ways, what I'm really doing is writing Firefox Sync from scratch, on company time.
Also, it really is more than system settings — I'm posting small bits of code.
It's not tooo hard to hide it. Since Git is decentralized, we can sync our changes like this:
This applies to both the Github stuff and my website — I intend to check my website into Git.
|(while at work)
||work laptop/etc ⇒ thumbdrive
||thumbdrive ⇒ internet