Live data from Hacker News

The more senior your job title, the more you need to keep a journal (2017)

hbr.org

31–40 of 135 posts

Re: The more senior your job title, the more you need to keep a journal (2017)

#31
post #9

Earlier quoted context omitted.

I do the same-ish thing. Main highlights on mine: 1) I start off the day with things I should be working on (samesies) 2) I use ### to demarcate different "working sessions" ... one for each meeting, etc. 3) I struggle with finding something that lets me: encrypt, search, big notes, and use multi platform easily :( Closest I've found was google keep so far .. but i hate relying on it like that. I'm pretty sure "somet…

There are many markdown based journal programs, some with encryption. Do these not work for you?

Can you suggest any in particular?

Re: The more senior your job title, the more you need to keep a journal (2017)

#32
post #6

I'm a software engineer, and I've been keeping a "lab journal" on and off for the past decade or so. A single markdown file per day, with the date as filename. First thing I do every day is copy the previous day's entry, give it a once over & remove what's no longer relevant. This helps me remember what I've been working on, and it's a track record of sorts. There's a todo list at the top of each day's entry. But the…

As I started to get more experienced (also software development) I noticed that more and more people were seeking out my help - which was frustrating, because I had goals I was supposed to be working toward myself. I found that keeping a log of each interruption and how long I spent on it eased my anxiety quite a bit: although I've never actually been asked to justify why it took "so long" to complete a task, having that documentation handy just in case made me a lot more pleasant to work with.

Re: The more senior your job title, the more you need to keep a journal (2017)

#33

Vscode has a nice journal plugin that uses a simple year month day directory structure, has convenient actions like open today, tomorrow and yesterday. 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.

Do you know the name of the plugin?

Re: The more senior your job title, the more you need to keep a journal (2017)

#34
post #6

I'm a software engineer, and I've been keeping a "lab journal" on and off for the past decade or so. A single markdown file per day, with the date as filename. First thing I do every day is copy the previous day's entry, give it a once over & remove what's no longer relevant. This helps me remember what I've been working on, and it's a track record of sorts. There's a todo list at the top of each day's entry. But the…

I'm curious as to how to implement this ? 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".…

Might I suggest checking out org-journal? It's a natural extension of the org-mode way of things, and integrates quite well with the agenda too.

Re: The more senior your job title, the more you need to keep a journal (2017)

#35

I'm not expert in meetings, but increasingly I feel like the modern approach of "everyone invited to the meeting is there to say something" doesn't work. 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 importa…

I’ve tried that but find the minutes have too much and too little. They do help me mix in my own notes.

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.

Re: The more senior your job title, the more you need to keep a journal (2017)

#36
post #10

Earlier quoted context omitted.

For this reason I try to write everything down twice. Once roughly by hand, and then a day or two later tidied up and put on the computer.

How do you find time for that?

In the words of the Merovingian: "Yes, of course. Who has time? Who has time? But then if we never take time, how can we ever have time?"

Re: The more senior your job title, the more you need to keep a journal (2017)

#37
post #6

I'm a software engineer, and I've been keeping a "lab journal" on and off for the past decade or so. A single markdown file per day, with the date as filename. First thing I do every day is copy the previous day's entry, give it a once over & remove what's no longer relevant. This helps me remember what I've been working on, and it's a track record of sorts. There's a todo list at the top of each day's entry. But the…

> I'm a software engineer, and I've been keeping a "lab journal" on and off for the past decade or so.

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.

Re: The more senior your job title, the more you need to keep a journal (2017)

#39
The biggest issue for me as a frontline developer is the backroom decisions that get made by seniors and architecture, that are subsequently poorly documented or communicated.

Every meeting should have a TLDR summary of what was accomplished that is shared with everyone that needs to know.

Re: The more senior your job title, the more you need to keep a journal (2017)

#40
Hmmm... the most important "paper skill" at my work is learning to "promote" papers across the tiers of journals.

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.

Post reply on HN