A few times a month I write in a Work Journal
A few times a month I write in a Work Journal
Intent is to remember years later what specific tasks I had, even if I've left the company and no longer have access to my files. It's been very useful during interviews when asked about details of what I did, and in conversation with friends who want to know what my day to day is like. I've learned that this journal has to be kept in a personal space so that I won't lose access to it during layoffs, for example. Do you have any similar habits? What are your policies?
Is the backpack you take to work with you considered personal space? Or can they rummage through that?
2Depends on whether or not they have local phys.sec and how much of an asshole they want to be.
2No phys.sec, but powertrippy HR...
1
google doc - can't be taken from me if I get laid off, the way a file on my work computer can
2We block google doc access on wifi (not that I use work wifi anyway, but still). Good suggestion!
1
This is a great idea! I keep a personal journal, in which I also write about work but not to this level of details.
What I do is to have a repository with experiments and other documentation. For example, when I try new programming languages or libraries, I put it there. When I learn new commands or tricks with commands, I put it there. I sometimes just straight write some documentation about something I did or learn and put it in the repository.
The repository is then highly searchable, and it has been vital for my work life. I've been keeping it since school times, so it's well over a decade old.
1That sounds amazing
2Yeah, I think it goes into a similar spirit to what you described, in the sense that you keep things in you in a format you can use later in life.
It wasn't always so orderly. It really started as a bunch of loose directories with different things. I only actually put it under source control recently when I decided to organize it a bit better. I was surprised with the things I found. Some I had forgotten. Like experiments with new libraries, or even trying programming languages.
1
I do the same thing - it's a brag book. I make sure nothing proprietary goes into it but it always stays at home. Mostly, I keep it because I use it as a source of information when I update my resume' every few months.
1