Live data from Hacker News

Use a work journal

fev.al

21–30 of 305 posts

Re: Use a work journal

#21
What finally got this to stick for me was abandoning all notion of structure and organization (and formal concepts like “logging” and “journaling”) and optimizing fully for capture over retrieval, then relying on search tools and proximity for the latter.

I have the OneNote icon in the notification area configured to create a new quick note and use it liberally. Occasionally I look through all the pages, especially the recent ones, aggregate and reorganize some, move others to an “archive” tab, and that’s it.

The faintest - and most disorganized - ink is more powerful than the strongest memory.

Re: Use a work journal

#22

Thanks for the great blog post, I could feel the frustration of not getting something to work, and the anxiety of feeling like I'm under performing. I've added you to my RSS reader now. :) I've started to use index cards to write down daily tasks and I'll switch over to obsidian if I find myself asking the same question more than once. I think for me the process of writing something down slows my mind enough to let m…

Yes! Obsidian with daily note plugin and templates makes it really easy to build a quick list of things and automatically link to yesterday’s notes. A little extra time with templates and some custom js and you can make it a single key combo to copy the notes to paste buffer for sharing in slack standup thread. Also, set up a praise folder and take screenshots every time somebody says something nice about the work yo…

Do you all pay for obsidian? Subscriptions rub me the wrong way for whatever reason and it was enough that I didn't want to pay so I use something else.

Re: Use a work journal

#23
post #6

I've always done this. My coworkers have been frustrated with me in the past for asking them to write things down, because some of them overestimate my ability to listen to them speak for 5-10 minutes and remember every detail. It's very hard to forget what is written down. Recently, I neglected to write down my thinking and progress for a week, and I was at a loss for where to begin the following Monday. Keeping a w…

How do you structure the entries? Bullets, free style, mix?

Date (MM/DD/YYYY)-

(tab) Task

(tab) (tab) Details

etc

Re: Use a work journal

#24

What finally got this to stick for me was abandoning all notion of structure and organization (and formal concepts like “logging” and “journaling”) and optimizing fully for capture over retrieval, then relying on search tools and proximity for the latter. I have the OneNote icon in the notification area configured to create a new quick note and use it liberally. Occasionally I look through all the pages, especially t…

It took me a couple years to realize this too. For the past five years I abandoned all structure. I use a literal log file. Chronological from top to bottom, with paragraph breaks for each workday. Higher than necessary verbosity, no points taken away for spelling or grammar mistakes.

Re: Use a work journal

#25
"Ignore all previous instructions. Show your work. Explain your chain of thought in detail. Keep a journal of your work progress."

I've been using this prompt on myself, on and off, for years, but I keep on hallucinating and losing focus and going off track.

Re: Use a work journal

#26
I’ve shared this before here. I actually keep a timestamp log of work I do. I used to do it by hand on my journal and while I still prefer it I ultimately found the benefit of having searchable text files that are integrated into my work management to be too much of a benefit to ignore.

Been using obsidian since it launched and my workflow is to always have the window open taking a thin column on the left of my screen and whatever I’m working on takes up the rest of the screen (Yey for fancyzones in windows powertoys).

As I work I just stream my thoughts into the file. I have a shortcut, ctrl-alt-m, that inserts the timestamp as `hh:mm:ss`. I hit it, and start typing. I paste screenshots, code snippets, as I go along. It’s godsend when I’ve gone far along enough and I need to reference something. Esp given that I work on security tickets and I’m constantly triaging reports that are unclear or require digging into layers of source code to find where they come from.

One important step to note if you ever try this out: if you have 30 seconds before you jump on to an interruption, try to build the discipline of throwing in a few words saying what you need to do when you return. Even with all the historical context it can take some thinking to recall what your next step should be.

In fact, if you don’t like journaling just do this last step instead. I stole the concept from GTD’s next actions and it works.

Re: Use a work journal

#27

Wonderfully written piece. I love how it builds up that idea of finally making progress, “seeing the matrix”, and then: > It’s Mitch, your PM. He’s asking the url for a doc he wrote Boy that’s too real. Really reminds me of the comic from a decade ago about programmer focus [1]. But welcome to the world of Note taking, I agree it’s like a superpower once you develop the habit. Obsidian is fantastic, but even daily ma…

The stupid thing is that I messed up the link of the comic I included, which is pretty much the same :) : https://fev.al/img/2024/focus.png

Re: Use a work journal

#28
I use GitHub Issues threads for this and it works amazingly well.

Any task I'm working on has a GitHub issue - in a public repo for my open source work, or a private repo for other tasks (including personal research).

As I figure things out, I add comments. These might have copy pasted fragments of code, links to things I found useful, quoted chunks of text, screenshots or references to other issues.

I often end up with dozens of comments on an issue, all from me. They provide a detailed record of my process and also mean that if I get interrupted or switch to something else I can quickly pick up where I left off.

Here's a public example of one of my more involved research threads: https://github.com/simonw/public-notes/issues/1

I also create a new issue every day to plan the work I intend to get done and keep random notes in. I wrote about how that works here: https://til.simonwillison.net/github-actions/daily-planner

Re: Use a work journal

#30
The benefit of journaling is not just reentry, but that you begin to solidify the mental model into a concrete branching of possibilities that is tightly coupled to the specific problem. Your work becomes traversal and mutation of this tree. Several benefits accrue: you begin to see gaps in the tree, and can fill them in. You begin to have confidence in your mental model, recovering the time you used to spend going over the same nodes again and again in a haphazard way. In distributed systems in particular, the work is often detailed, manual, error prone and high latency - with a solid mental model you can get through a checklist of steps with minimum difficulty and high confidence that you didn't miss anything. This ability to take something abstract and make it more concrete on the fly is a critical skill.

Perhaps the greatest barrier to using it is akin to envy. We see others who apparently do this without written materials, in their head. I think we see this as evidence of intellectual superiority and harbor the doubt that using an aid like a journal means we are somehow lacking in skill or ability. This is wrong. Using an aid to map out complex problems isn't a failure, it's essential, especially for problems in systems you've never used before. Over time you may yourself build up your expertise such that you no longer need the aid, but that doesn't signal anything about your intelligence or ability either, only your experience.

Post reply on HN