Live data from Hacker News

Use a work journal

fev.al

171–180 of 305 posts

Re: Use a work journal

#171
post #156

Evey time I've tried essentially journaling for my own sanity I get too bogged down in the way to actually do it. Logseq and Obsidian are often mentione but by the time I've figured out how the hell to use thier obscure syntax (why the hell am I programming, its a journal) I've lost interest. I'd like for there to be an out of the box option, but there doesnt seem to be any. When you bring this up in discussions like…

Have you tried appending a txt file? If you want to find something, grep it.

Re: Use a work journal

#172

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 o…

I write a lot of notes in fact I write more than I read. It helps. However I have some issues: 1. How much commentary should I write? I try to write not too many notes because I write code, and some say code should be self-documenting. So it's the same old question of how many comments should there be along the code. 2. How do I retrieve a note I've written earlier? I can use tags and search for them but it is not ea…

> a balance between "Just do it" and "Write about it"

This is the key point - capturing, organizing and retrieving notes has a cost. And I find myself always paying for notes out of my "just do it" budget. Especially when virtually all of the things I'm working on (notebooks, libraries, applications, planning documents) are themselves a form of writing, having yet another place to scatter my thoughts is not helpful at all. It's much more productive to take that thought and put it directly into the project documentation where everyone can benefit. More README, less journal.

Re: Use a work journal

#173

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 o…

> 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. I wrote a program (used from a CLI, but I mostly use the GUI I developed for it) to do something similar for my own use: https://github.com/lelanthran/frame/blob/master/docs/FrameIn... I use it daily.

It's low-tech, but I've been using notebooks (not too thick, stapled usually). I write a header for each day when I start and then a line or two as I work on tasks and I try to note each time I switch tasks.

I keep the notebooks but rarely look at them once they are filled. Maybe once or twice as I switch to a new notebook and then once again when it comes to yearly review time. A couple of times I have rifled through old ones looking for command line flags but most of the time reading through the notes is enough to jog my memory.

Re: Use a work journal

#174
post #156

Evey time I've tried essentially journaling for my own sanity I get too bogged down in the way to actually do it. Logseq and Obsidian are often mentione but by the time I've figured out how the hell to use thier obscure syntax (why the hell am I programming, its a journal) I've lost interest. I'd like for there to be an out of the box option, but there doesnt seem to be any. When you bring this up in discussions like…

It took me a few times to land on something I stuck with. At my current job I have a running doc where I just start a new entry per day, at the top and log before I try to do something, and what progress I made that day.

What maybe helps is this doc is findable and readable by coworkers and my boss. It is very useful for me, but it's also helpful for others to see what I'm working on without pinging me.

Re: Use a work journal

#175
I like having a "devlog.md" file for each project/repo.

The log is jut a reverse chronological order of comments/todos/rants.

I have mapped on VSCode cmd+shift+I to write a timestamp. Whenever I want to write something I just insert a timestamp at the beginning of the bullet-point list and write it out. This is stored alongside the repo.

It is particularly useful for recovering in the morning where I was the night before.

Re: Use a work journal

#176
post #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 w…

I use GitHub issues (combined with embeddings and logprobs via your llm) as an AI infused bookmark manager:

https://GitHub.com/irthomasthomas/undecidability/issues

The code that runs it is here:

https://GitHub.com/irthomasthomas/label-maker (how it started/how it's going:)

Re: Use a work journal

#177
While I wholeheartedly agree that this approach makes perfect sense and would perhaps help with context switching various tasks, the time required to pour your heart out journaling would take time away from doing actual work.

While I do some note taking at work it's all one liners, url references, copy and paste code snippets and VM options for intellij.

Re: Use a work journal

#178
post #156

Evey time I've tried essentially journaling for my own sanity I get too bogged down in the way to actually do it. Logseq and Obsidian are often mentione but by the time I've figured out how the hell to use thier obscure syntax (why the hell am I programming, its a journal) I've lost interest. I'd like for there to be an out of the box option, but there doesnt seem to be any. When you bring this up in discussions like…

If all you need is daily notes, Obsidian does that out of the box. You don't have to tweak anything, install any plugins or learn any new syntax if all you need is a simple GUI over text files. It's not open-source however.

Don't get fooled and intimidated by the "productivity porn" community that likes to show off their sophisticated setup and unrealistic workflows. My rule: if they refer to Obsidian as their "second brain", they are part of the cult and should be ignored.

All that said, I strongly encourage you to try pen and paper, the ultimate, no setup, open source app. And it has exquisite haptic feedback on top of that.

Re: Use a work journal

#180

Earlier quoted context omitted.

Same here. Taking notes is incredibly helpful, especially when I'm stuck or unfocused. I just start writing anything that's on my mind and it's like the writing does the thinking for me. While I used to type notes digitally, I've recently discovered the superiority of pen and paper. Writing by hand offers more flexibility - you can start anywhere on the page, sketch, or create mind maps effortlessly which encourages…

Both digital and handwritten notes have their values. - I‘ve used moleskine notebooks and fountain pens for over two decades. Fountain pens are unbelievably smooth to write with, and the text looks beautifully. So I can relate to your experience. Re Keyboards: I switched to mechanical keyboards lately and will never go back. It’s like the fountain pen of typing.

I wholeheartedly agree on mechanical keyboards.
Post reply on HN