The more senior your job title, the more you need to keep a journal (2017)
hbr.org
hbr.org
There's a todo list at the top of each day's entry. But the rest is mostly free-form. Some days don't contain anything. Others contain meeting notes. Design ideas. Results of experiments. It's all plain text, so it's easily grep-able. Sometimes I look back at them to answer "why did I do that"-type questions. Sometimes $manager wonders what I've been working on or why it's taking so much time. I can just point at the journal and say "I've been doing 3 meetings every day and I've been onboarding people so I haven't had time to work on XYZ".
It's not much effort. And imho it's definitely worth it.
The number of times this has saved me time figuring out "Oh .. i saw that error before .. how did I fix it?" and "who did i talk to about X and what did they say" months to years later has proven to be super helpful and I will be continuing indefinitely.
A HN search illustrates the amount of markdown note apps available: https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...
I use Zettlr as a markdown editor, with the underlying directory being in git. It's not encrypted, though doing that should be pretty easy with something like EncFS.
Open-source. Encrypted if you want. Synchronized using WebDAV (also Dropbox, NextCloud and OneDrive). Uses markdown. Has tags. And apps for everything (Windows/macOS/Linux/Android/iOS/terminal).
I'm curious if there is something you are using on mobile for vimwiki? I've been using termux on Android, which works well enough.
My backup method is pretty simple but it’s been silently chugging along for months now without a single hiccup. It’s just a git commit via cron job: https://thelinell.com/using-vimwiki/
What I eventually ended up doing was moving to vscode. I use it my main IDE for the last couple years. I have a linux vm running for all my development, with vscode remote ssh.
- I keep a folder for each month - I have a file in each month called YYYYMM-dailies.md, level 2 headings for each day - Notes that grow too complex for the "dailies" get their own file in the folder. A number of these might get polished and copied into a document site somewhere. - Sometimes I'll make a subdirectory of "snips" with small scripts or pseudo-scripts (stuff to copy/paste) - The integrated shell lets me paste commands into my dev vm and copy the results back into my notes.
A feature of this is that while it's not really "synchronized", I can vscode-remote-ssh from multiple machines, or just ssh into the vm to get my notes. You can use rclone or keybase+rsync to backup the notes directory (or keybase's git if you want to check notes in).
Another
I mean, i currently put everything that needs doing into org-mode, clock in on the task when i'm working on it, and clock out when i'm done. Mark the task completed, and archive done tasks daily to an archive file.
I guess that's the limit of my daily "todo" activities. It's mostly in point form "x needs doing", "request confirmation from x", "send status on project x to y".
If i'd have to do it in a "daily file" i have no idea how to structure it. Todo'ish lists probably wouldn't work. They're either done or they're not. I guess it would have to be more like "short stories".
I think what works best depends upon how you plan to use them and what your workflow looks like. But I have tended to find the "1 giant file" is a better fit for me.
I've recently started contracting (and billing hourly) so I've switched to using an org-mode file, which contains commands, links to internal stories, and other things.
As I'm contracting I figured I might be asked to justify the hours-billed, etc. So for the first time I'm explicitly writing the daily-log with the expectation that I'll share it, and the employer will see what I write.
That (perceived) level of scrutiny has really improved the detail and coverage of what I document.
But good comment, thank you!
Some days I wonder where the day goes, with interruptions and getting back in the zone, it's a miracle anything gets done.
I studied (a mix of EE/CS) in the EE dept., and we were actually taught to do keep such notebooks/journals, as in electronics labs were assessed on what the contents of your lab book, not on what you'd produced or measured (or at least not 'hey lab assistant look at my 'scope, see, done it' - obviously measurements would be recorded, but then the assessment's more 'why' and 'was that expected' than just a copied value from a neighbour).
I hated it at the time and wasn't particularly good at it ('writing what I'm doing just slows me down and distracts me from doing') but I've worked in software engineering since and wished I'd stuck at it. I've briefly tried in fits and bursts but never maintained it as 'this is how I work', despite having a former colleague who did.
Probably time I tried again, I agree it's worth it.
I try not to be strict about the format, and it's certainly evolved over the years.
For instance, we have a weekly department meeting. There's now a section "Dept Meeting" in today's file with a few points I want to bring up. Maybe they'll get resolved by then, or maybe I'll add more points. The simple act of copying that file each day and removing what's no longer relevant means I have refreshed my memory, don't have to worry about stuff that's no longer relevant, and have a track record of what I thought was relevant.
I run "vim `date -I`", which opens a file for the current day in the form `YYYY-MM-DD`. I keep it in a git repo that I commit and push to every time I add a note.
I separate topics using `===` surrounded by blank lines. When I go back to update a topic I already wrote something about, I separate it with `--` surrounded by blank lines.
The main thing this ends up being useful to me for is that I put off filing my timesheets until the end of the month, and then when our accounting lady gets after me, I can go back and actually write down semi-accurate notes on what I did each day.
vim $(date -I) alias jim=' \
journaldir="/home/myusername/journal/" ; \
jfile="log_`date -I`.txt" ; \
jfilepath="$journaldir$jfile" ; \
echo "Creating log: $jfilepath" ; \
vi $jfilepath ; '
Instructions:(1) Copy to your .bash_aliases file.
(2) Edit the journaldir, and replace myusername with your name.
(3) Create a journal directory somewhere for #2.
(4) Source it. source ~/.bash_aliases
(5) jim will open up today's note in Vi.
Try it out, and let me know.
alias journal="vim ~/workspace/google-drive/journal/$(date "+%Y-%m")"
Then in vim I have this mapping, by pressing F2 it opens a new line at the end of the file so you can just start typing.
I add goals to the beggining of the week with the F3 map. nnoremap <F2> Go<NL><Esc>i<Esc>"=strftime("\%A, \%Y-\%m-\%d \%H:\%M:\%S")<CR>po -
nnoremap <F3> Go<NL><NL><Esc>iWeek <Esc>"=strftime("\%V ")<CR>p<Esc>i goals:<CR> -
Monday -> Press F3 -> like a bujo, review what is still relevant and move to next week or drop it. Week 10 goals:
- [ ] check connectivity with service x, splunk and service Y, from new environment
- [ ] xxxx
Then whenever I will change context in my mind I just go back to the open buffer and press F2.
I normally start my day looking at what happened over the other remote branches, and update my weekly goals task list Thursday, 2020-07-09 08:25:52
- emails / slack
Thursday, 2020-07-09 08:36:13
- support x person
Thursday, 2020-07-09 10:00:00
- dog break
Thursday, 2020-07-09 10:00:00
- HN
Then at then end of the year I create a folder `archive/201X/` and move all the files under it.I had a calendar event reminding me to review what happened over the week on Friday afternoon, but that is just lying to myself. I got to do once or twice over the last couple of years, that is something I need to improve on which is the whole point of article, review it while it is fresh and learn from it.
edit: code format
Check out my other alias, in the sibling comment. I improved on it.
alias jim=' \
journaldir="$HOME/journal" ; \
year="`date +%Y`" ; \
yearpath="$journaldir/$year" ; \
[[ -d "$yearpath" ]] || mkdir -p $yearpath ; \
jfile="log_`date -I`.md" ; \
jfilepath="$journaldir/$year/$jfile" ; \
header="# log_`date -I`\n\n# Highlights:\n\n" ; \
[[ -f "$jfilepath" ]] && echo "Opening log: $jfilepath" || { echo "Creating new log: $jfilepath" ; echo -e "$header" > $jfilepath ; } ; \
vi $jfilepath ; '
Copy this to your .bash_aliases file. It's fully automatic. It'll create the directories automatically.This will now create a /home/user/journal/YEAR/journalfile.md. It's now separated by year, so that you can run this forever, and have a maximum of 365 files per year directory.
This is a markdown file. And in the header variable, I had it fill in the new file with some basic headers. You can edit this yourself to add more.
Try it out, and let me know.
on macos
Try this instead. It works for me. Let me know.
Copy it to your ~/.bash_aliases. And source it.
alias jim='
function _jim() {
journaldir="$HOME/journal"
year=`date "+%Y"`
today=`date "+%Y-%m-%d"`
yearpath="$journaldir/$year"
[[ -d "$yearpath" ]] || mkdir -p $yearpath
jfile="log_$today.md"
jfilepath="$journaldir/$year/$jfile"
header="# Log: $today\n\n# Highlights:\n\n"
[[ -f "$jfilepath" ]] && echo "Opening log: $jfilepath" || { echo "Creating new log: $jfilepath" ; echo -e "$header" > $jfilepath ; }
vi "$jfilepath"
}; _jim'I get caught up trying to design the best system, and end up with something that only half works -- I just post notes to myself in Slack, particularly in the @you channel, the one it sets up for you at your username. Downside: every time I switch jobs, I lose a TON of context. Upside: everything's in Slack and I don't have to worry immediately. :) Plus, it's always possible that I'd lose the computer I was taking notes on, or not allowed to sync notes to my own private repo, or whatnot.
If I need to write longer-form notes than Slack allows, though, I often turn to Notes app or OneNote (if on Windows). But ... it's constrained because I end up not being able to stick with one cross-platform note taking tool -- the tools I use are too different. Still waiting for the perfect tool that has yet to arrive... I suspect the answer lies in the operating system -- to track what I work on in any app and helping me surface and record metadata better. To move from tracking files and folders to helping me track activities and outputs/decisions. Integrating git commit logs with macOS-like app-based revision history with operating system file browsing (for other kinds of cloud storage) seems like the right level of abstraction to work at, but I'm not sure what the right UI would be. :)
I make entries for each meeting, date, participant, notes, incoming and outgoing tasks. Also adding in sketches, designs, and other stuff that I wanted to write when I didn’t have a computer near.
I started this because I found having a laptop or phone out during a discussion with someone off putting. People would open up if I was jotting small notes but would not if I had a laptop open.
I can keep the notebook in my front pocket. Started out with hardcover moleskines but am not trying out rhodia, leuchtturm, and others.
Each one lasts about 3 months and I have a stack 4 feet high so probably 10 years or so.
Actually having 5 lying in front of me, 5 ideas (remarkable in my opinion) One sayin: "Cumulative acting 'deductive'"? P-:
Somebody told me: 'Fine, than I am now able to shred all my documents, conserve a digital copy and further taking only small sheets of notes.'
> dear But... ^^
One just cannot be as expressive in markdown as one can be on a blank dotted-grid page and a pen-pot of Tombow double ended brush pens and Pilot V5s.
Anything important can be digested into markdown, but with a note to the journal page where the magic actually happened.
(It’s too bad that magic usually turns out to be gibberish thought spam.)
Pilot V5 RT refills fit into the Everyman Grafton pen ($35)
I used that for a while but found the pen a bit too large.
Nowadays I either use an Energel [2] or the classic Pilot V5.
[1]: https://everyman.co/collections/frontpage/products/grafton-p... [2]: https://www.amazon.com/gp/product/B0776M8VY1
EDIT: Does anyone else know of any companies like this for office supplies? Notebooks, pens, inks etc.? I support Noodler's Ink since they are entirely US-based, but even they have some of their pens made in India etc.
Counterpoint: Yes they can.
There’s this weird fetishization about paper notebooks. It’s like the people who say that vinyl is unequivocally better (it’s not).
For some people the end result of digital notes is vastly superior to anything they can scribble in a notebook.
Paper offers a different level of expression. The comparison is thus not equivalent.
Usually when you offer a counter point you don’t just disagree, but provide some basis or example to show the statement or proposition in question is false.
Fetishising notebooks aside, parent mentioned expressiveness. Clearly everything that can be _expressed_ in Markdown can be expressed on paper, but it’s not clear that the opposite is true.
Regarding my original point, it’s what you use to get to the finished product that counts, and I maintain that hacking markdown is inferior to freeform pen and paper thinking.
It has built in OCR so a search will find my handwritten notes as well.
> The novelist Paul Theroux has said that he writes long-hand because, “The speed with which I write with a pen seems to be the speed with which my imagination finds the best… words.”
Before this switch i would default to using memory. It was easy, it worked, and i have a rather good memory. Most things worth remembering somehow just "sticks" without any mnemonics.
After the switch, i got 10x the information i used to get before, and while i initially settled on using my inbox as a "todo list", flagging items that needed attention, this also became rather inefficient after a while.
I started keeping a journal. Every meeting i go to, i jot down notes, every agreement is written down. I still keep my todo list, but it's in Emacs org-mode now. Notes are handwritten.
As the author also hints, handwriting helps commit things to memory, so the times i actually consult my notes are rather rare. Instead, by simply having written them down, my brain somehow accepts that "it's under control", and focuses on something else, but still remembers it.
I also put references to my (page-numbered) paper notebooks in my notes file, and vice versa, so stuff that would be very long to transcribe doesn't usually have to be transcribed at all.
Helps me clear my mind, and it saves me a lot of time in the morning, because I can start work and have some wins for the day within 15 minutes...and that momentum carries me through....
Also, the shut-down period is nice, because when I'm tired at the end of the day, it doesn't take a lot of energy.
I also have a pretty strong aversion to headless-chicken-mode, having seen it as a pathological disaster spiral at a couple of places where everything is urgent all the time, and so you never have time for anything. Being in too much of a rush to do things properly is a trap.
I find as an employee I have to fill and empty my head a lot. I have a good short-term memory, but things that I don't write down tend to slip out after a week or two. "Oh, I worked on that thing? I don't remember that."
I find the absolute opposite to be true- At the time of the lecture or meeting or whatever, I am just trying to capture everything. What is truly important and what is noise is not clear to me at that point. Also in the beginning stages of a class or project certain concepts or decisions seem very new or foreign, and a few months later they are deeply ingrained and no more likely to be forgotten than understanding what gravity is.
By far the most successful study technique I have ever used is recopying my initial notes. The second set is much more coherent, organized, and focused on the tricky bits while removing things that I thought might be important at the time but ended up not being important.
I think someone did you a major disservice 30 years ago.
I'm not sure how I would achieve it though? The right initial structure isn't usually clear at the beginning of a conversation/research session/whatever I am taking notes on.
Someone who has nothing to directly contribute to the meeting needs to be present to keep the goal of the meeting in focus and ensure a single shared outcome at the end. Yes it's slower, sometimes less efficient and sometimes deep subject matter knowledge is important, but six people leaving a meeting with their own accounts of what happened is almost worse than no account. Wherefore art thou minute takers?
Once that is in place, then many of the comments in this thread about needing personal notes to remind them about what to do and when, or what the team agreed to do next, surely are no longer necessary?
When everyone can rely on that, then by all means keep personal meta-meeting notes about emotional response, etc. for reflection. I think that's something I would like to work on.
I’ve experimented with having a meeting wiki where everyone keeps notes in a single file, that was pretty good. But suffers from “open laptop syndrome.”
I heard someone suggest, and want to try, assigning the note taker at the end of the meeting. I’m not sure if it’s cruelty:effectiveness ratio may be too high.
According to Roberts Rules, the #1 order of every meeting is everyone agreeing that the previous meeting notes are correct. Only after the previous meeting's minutes are finalized do you proceed with the current meeting.
----------
A surprising number of people do not know how to run meetings. As such, most meetings wander off unfocused. And since most people fail to solidify meeting notes, action items from previous meetings are "lost".
It takes work to ensure that meetings are worthwhile. And very, very few people seem to know the secrets (despite them being very obvious and well documented).
- creating a short recap of what happened
- the above recap can also be shared with team members who couldn't attend (e.g. home sick or APAC based)
The latter has been incredibly useful during COVID specifically and for remote management in general.
If the meeting is complex and the chair has to get involved (e.g. to adjudicate) then they often will be too busy to take the notes themselves; I for one cannot steer a discussion and take notes at the same time. This is also a good way to introduce competent juniors to meetings - make them the record taker (they need to be be briefed first on what is expected). Even tracking who people are can be quite challenging. If there are lots of new faces (e.g. external reviewers) the chair may need to get people to introduce themselves (name and role only, not a bio), and the meeting recorder can concentrate on matching faces with the names on the invite list. If the meeting is in a conference room, writing names around a little picture representing the table can help with this.
Finally, in the sense that history is written by the victors, owning the minutes can be quite a powerful position.
Seriously, a good secretary, even one shared amongst a team, could be a huge time saver. Meeting minutes, meeting invites, catering, visitors, errands. Why did this role disappear?
Habit is the main journaling challenge, a fact barely touched in the article. There are two habits that need developing simultaneously: taking notes and reviewing notes. It’s true that simply writing something down leads to better recall, but that’s not what the article is about. The article is about creativity.
To make something based on your past observations you have to review and synthesize. That skill is much different than taking notes to remember stuff.
I agree with the author that there is nothing better than pen and paper. But There are scenarios where all I have is my phone and I still want to take notes. This leads to another can of worms: how to organize all the notes you generate on a daily basis.
I built a general purpose note-taking tool [0] to help me develop the habit of taking and reviewing notes. It has also become my repository of snippets of information generated from my phone.
I use the snippets I create to inform writing I do elsewhere: documents, outlines, letters, etc.
A few months and teletraces later his journal was thick enough to publish into a book, so he did exactly that.
Ten years later, I had used about 5 pages of mine. My two teammates wrote more, but none of us went past page 50 or so. OTOH, the scientists we worked with had gone through multiple books by that time.
It's not an easy habit to get into.
One thing I'll note is that the hand-writing -> text converter never really worked that well for me. I have messy handwriting so YMMV. I would still recommend it, but if that's the killer feature for you it's something to keep in mind
I've been thinking about getting an iPad to take notes on, but I see the ReMarkable tablet pop up all the time (thanks to their marketing, I guess it's working), have you tried taking notes on something else?
I'm mainly just thinking that if I'm getting a tablet for notes, should I get one that's practically _only_ for taking notes (ReMarkable) or one that has much more functionality (iPad). I guess that also depends a little bit on the "syncability", does the ReMarkable have integrations to sync notes and documents to third party services or do they roll their own thing?
I bought it to be an e-reader, but ended up taking a ton of notes in it. I have notebooks for projects, for recurring meetings, a single-page "task list" and a page-per-week notebook tracking what I plan to do, what I did, and what I learned, which I use to inform my part of weekly standup meetings.
I prefer to keep most notes ephemeral; if it matters, I should be transcribing it elsewhere (preferably to something typed; I have some shame about my handwriting quality). I do keep all past weeks of my standup notes, and I expect to draw on them heavily to inform performance reviews and promotions, but I can go through them in order, so even there searchability is not a big loss.
It's PDF capabilities are fine, and you can write on the pages which is nice, but I've not really tried to access any of these notes outside of the device. The did roll their own cloud sync capabilities though so you can use their apps on devices for that. There's also the 3rd party options that exist for that too.
As mentioned by jagraff they expose ssh and allow you to login as root. The whole device is a linux machine so if you want to setup syncthing to run on it you can[1]. If you want something else like zotero, or google drive, I suggest checking their wiki[2] and the github repos[3] dedicated to curating some of the stuff written for it
TLDR; Super happy with remarkable v1. So happy pre ordered V2. It gives you root on a linux box.
[1]: https://github.com/evidlo/remarkable_syncthing
Funnily enough I actually love notebooks, but I cannot for the death of me keep a neat and nice design when keeping notes using a physical notebook, which means that I loose all motivation. However, having a minimalist tool like jrnl helps me to actually write, not just collect blank notebooks.
Defaults to markdown which is ideal.
There is also a nice insert date time plugin so you can time stamp your entries more easily.
It's a fluent setup.
I use the blank side during calls to jot down notes which I transform into meeting summaries and email later. Then I clear it.
I find whiteboard writing very satisfying and the the fact it’s always out there in the room with you - can’t minimize it or just not open it - keeps you always synced to your tasks. Space is limited so it’s always relevant. You’re at some point forced to take care of things to make room for new things - can’t scroll down.
I used to use Evernote, but it got unwieldy and Apple Notes did everything I needed it to.
Very likely, if you write down notes about work-related activities they are the property of the business.
So, who has physical journals from current and previous jobs at home, and how many people have electronic ones on systems other than corporate approved/internal ones!?
I'm not judging, just saying!
Last year I took a senior manager position at a fairly large company. I am also building a side project (not competing, totally unrelated). Between those 2 things my mind is constantly full.
I depend on my project plan to move through time / between tasks. But I still depend on my memory and a high volume of unstructured notes to move through small increments of time. You simply can’t plan every single sub task.
I have noticed when things get really busy and I start getting tired, everything around me speeds up. I really like the idea in this article that writing a journal by hand slows life down.
I’m going to try structured journaling. This year’s Big Project is about to go live, and I need a way to slow it all down for a few minutes each day.
I ended up building a product (https://www.friday.app/) to make this easy and automated. While it's built for teams to share updates and reflect (think weekly updates, retros, etc), there's "single-player" mode available too.
I like the digital journal format because I could never start the habit with paper. The automated reminders were critical to establish the habit. I still keep a regular notebook where I'll document thoughts, but it's more ephemeral.
At the time I was using raw yaml, but eventually transitioned to emacs org-mode.
I still do it personally and find it invaluable. I still heavily use moleskins, but regularly sit down to transcibe them into digital form, but don't throw the physical notebooks away, just in case.
The most feature thing for me is I can use my tablet. Dealbreaker otherwise. I’ve been looking at Notion but their iPad app was trash last time I used it
Besides don’t hunch and don’t get fat, “keep a journal” is what I would tell my younger self
This is how I get to keep journal, by having it as a 5 letter command in the terminal.
For the past several years it’s been in the form of a git repo of text files, more or less by date append only.
I can’t imagine not having one now.
OneNote is also now free.
It started as a simple Todo/done log, but then I started using for notes and general scratchpad.
1. Loose-paper and Whiteboards -- Sketches and concepts that rarely last longer than 5 minutes before being erased or trashed.
2. Short-term journal -- When a concept needs to stick with me for 1-day or so, I write it down into my short-term journal. This is a tiny Field Notes journal I keep in my pocket, always accessible. This journal is extremely tiny, and thrown away on a regular basis (Well... more like thrown into a bin. I don't think I've re-read any of my old ones, but I do keep them just in case). I rarely visit anything aside from the most recent 3 or 4 pages.
3. Long-term journal -- Some concepts need to stick with me for more than a day. These I copy into my long-term journal. Anything in the Long-term journal is indexed... yes, documenting your documentation. If its important enough to be long-term archived, its important enough to be thoughtfully organized and categorized for quick recall. I suggest a journal with multiple bookmarks and pre-numbered pages, such as the Leuchtturm1917.
My first "long term journal" was a standard $1 80-page spiral notebook. If you manually number all the pages, then you're going to be well organized. Once you're familiar with an organizational scheme, upgrade to a Leuchtturm. (Moleskins don't have numbered pages...). Some people prefer dates instead of numbers: it really depends on what organizational scheme works for you.
4. Team Activity -- Anything requiring coordination with others becomes a team event. Usually an email, but it could be a note on a desk, or a message left on their whiteboard. Or a formal Jira issue ticket.
---------
The important thing to note is the hierarchy... from ephemeral whiteboard all the way up to formal team coordination.
Generally speaking, your notes should traverse the tiers up and down as needed. This means copying notes over-and-over.
As computer wizards, we are often familiar with the computer automatically copying our work for us. In the paper world, you must copy notes manually. Despite its tedium, copying notes from one tier to another is extremely important.
Writing a note directly into your long-term journal probably means getting the concept wrong. You should get a first-draft figured out somewhere else first (whiteboards). Or, maybe a concept isn't "deserving" of a slot in your long-term journal yet. Keeping it in your short-term journal first helps "reduce the noise" found in your long term journal. Even if you know something is important enough for the long-term journal, keeping it in the short-term journal first can help you figure out how to properly organize it.
Finally: Copying notes within the tiers is a form of meditation that helps solidify and memorize ideas. If something is truly important enough to traverse the tiers of organization, then its probably something you want to store into brain-space.
-------
Teammate communication is simply another tier. You definitely want to get your thoughts and concepts figured out before communicating.
I tend to use a lot of paper for notes as well, and this hierarchy is interesting.
My biggest issue is I do not regularly review my notes. And I know that there are valuable pieces in my notes.
And I hate copying notes over, because of the time taken.
Your post is giving me pause and I am reconsidering the value of rewriting.
Every meeting should have a TLDR summary of what was accomplished that is shared with everyone that needs to know.
The first is that I simply couldn't hold everything in my head anymore because I had to track 5-10 different projects at any time, and context switching without something written down sucks when you have to context switch multiple times a day.
The second is that writing things down was a great way to force myself to clarify my thinking. I became more articulate across the board, not because I got better at bullshitting, but because I was now reserving time in advance to think through open issues in a structured way.