One single text file per year named journal .md in Markdown edited in an always-open window of a text editor (VSCode) throughout the day. Oldest entry is at the top, newest is at the bottom. To-do items are below the newest entry so that I they are always visible. For me the most convenient thing is that I can use the editor's search feature to find things. There's no specific format (no tags, for example). There is…
Thanks for the detailed reply! I like the idea of a monolithic journal per year. How long have you been at it (if you don't mind me asking)?
Ask HN: How do you take notes throughout your work day?
11–20 of 91 posts
Re: Ask HN: How do you take notes throughout your work day?
#12For technical things where I'm a newbie, I'm trying to learn-in-public [1]. I write a TIL usually at the end of the day, it typically goes quickly. In those cases where the matter is private (maybe 1/4 of all), I attempt to document it in company's knowledge base or at least share it in the company chat. All other things go to my personal Obsidian. [1] https://marcel.is/tils/
+1 on Obsidian I quite like the categorization on your site. Do you have a background in tech or are you coming from a different industry?
Re: Ask HN: How do you take notes throughout your work day?
#13I do this for a few reasons.
1. Taking notes on a computer during meetings is disrespectful IMO. Every time I see people do it, 80% of the time they are checking email, checking a site, looking up stuff instead of paying attention to the speaker or meeting. I get pissed when people spend the meeting looking up alternatives just to challenge the person speaking. It isn't that challenging an idea is bad (it is critical in fact), it is you need to listen to comprehend and not listen to respond.
2. The vast majority of notes are worthless after a few days. They were relevant to complete a task but not noteworthy for my career or to learn something I need to keep forever as a reference.
3. Writing something makes me personally more likely to remember it.
In the 5 subject notebook, I keep the sections as "Meeting Notes", "Active project(s)", "Design", "Personal notes" and the last one is usually open for just misc crap that I don't need to categorize right now. The design part I almost always take pictures of and put in my notes app, but I only take the pic of the final design and the notes on why. Design here is typically software architecture type design, product design, UX etc. It is faster for me to sketch it then to try and put it in an app.
I've done this for my entire career, 20+ years now and just refined over time. I also am a huge fan of note cards during the week while I am working. For example, I'll write my plan down for the day/week/month on a note card and then work through it. The time period is chosen based on what I am working on at the time, and sometimes I have one for a day, one for the week, one for a month etc. Just helps me keep myself organized, and again, writing it forces me to remember better, personally.
As for using it, I have gone back and used stuff in the past year that I wrote down 15 years ago. Typically this is more design concepts or how to solve an interesting problem, or what were issues I ran into using XYZ design or module etc.
Re: Ask HN: How do you take notes throughout your work day?
#14One single text file per year named journal .md in Markdown edited in an always-open window of a text editor (VSCode) throughout the day. Oldest entry is at the top, newest is at the bottom. To-do items are below the newest entry so that I they are always visible. For me the most convenient thing is that I can use the editor's search feature to find things. There's no specific format (no tags, for example). There is…
Thanks for the detailed reply! I like the idea of a monolithic journal per year. How long have you been at it (if you don't mind me asking)?
Re: Ask HN: How do you take notes throughout your work day?
#15Re: Ask HN: How do you take notes throughout your work day?
#16Re: Ask HN: How do you take notes throughout your work day?
#17Re: Ask HN: How do you take notes throughout your work day?
#18- Vim-like bindings that don't suck
- Growing and fantastic set of community plugins, including a presently-in-alpha plugin offering Jupyter support (!)
- Markdown-based wiki-type thing, with mobile, sync, and publish support
- Wide range of pleasing themes
- Development is active and is proceeding relatively swiftly; there are new versions available quite often (it's self-updating)
- Electron UI, which I know raises some eyebrows, but in my experience it's comparable to e.g. VSCode in zippiness (so: not terrible, good enough)
Disclosure: I'm working on obsidian plugins, and I paid for a commercial license, but I'm not in any other way associated with the project, i.e. I don't see myself as plugging myself here.
While not FOSS, it's an impressive indie project that I'm enamored with.
Re: Ask HN: How do you take notes throughout your work day?
#19At the end of the week I review the notes and if it's important enough I rewrite the notes on a personal wiki.
For notes I have a(n) (paper) agenda with on the left the week overview and on the right notes. Best agenda ever. https://www.bol.com/nl/nl/p/castelli-agenda-h83-2020-2021-18.... All remaining notes I write on empty A4 paper.
Re: Ask HN: How do you take notes throughout your work day?
#20The "blog" notes are one page per task, linearly organized. It could be a Jira issue, or something that needs to be done but is not in Jira. The note contains anything relevant to the task: the specification, what I found, what I plan to try, what I did. After the task is completed, I leave the page and usually don't edit it again. If later there is a problem or someone asks something related to the task, I will look it up.
The "wiki" notes are hierarchically organized, and contain e.g. company processes, contact list within the company, individual projects, frequently used software or frameworks. The notes are my extended memory, I refactor them as needed. The idea is that I need some information repeatedly but in long intervals, and it is more convenient to quickly find it in my notes than try to remember, try to find, or ask people.
Technically, I use either OneNote or CherryTree, depending on what the company allows.
I mostly use paper to sketch database relational diagrams. If my task requires me to write a join across several tables, I will design it on paper, write the code, then throw the paper away.