I then use these notes to plan out the problems, store personal research and organize code snippets. That makes it easy to link to from my weekly notes, and gives me a loose idea of when I was working on which tickets through backlinking. When I begin work on a non-trivial ticket or project, I make it a note in my Tasks folder named with it's Jira tag. After the todo list, I put down a heading for each of my meetings/activities that I want to take notes for and fill them in accordingly. I have a subheading for each day, and a subheading in each day for a todo list. At the beginning of each week I make a new Weekly Notes page. Inside it are folders for Weekly Notes, Tasks and Information. I started up a job a few months ago and threw myself into Obsidian, and it has definitely been paying off. Also, since notes are just files stored in directories, I have all sorts of shell/Python-scripted automations and shell aliases to quickly do stuff. Obsidian is extensible at hell, but I'm not spending all day looking for new tweaks, I'm just writing notes. I don't have any comment on the blog post in the article, because this system works really well for me. I store checklists, procedures, howtos, concept summaries, cheatsheets, and a daily log stored in a YYYY-MM.markdown file. I personally just create atomic (single-topic) notes, with tags in the YAML front-matter, and store them in a folder structure along the lines of the Johnny Decimal System. Jamie Rubin's blog series is pretty good, too. Despite appearances here, I am not a notes fetishist, so I find his videos rather approachable especially his "Start Here" video. Of course it does.īrowsing through Linking Your Thinking's YouTube channel might be a good first-start. His business Indie Thinkers seems to share a market with many personal knowledge management tools. Maybe with this post the author got a little lost in the knowledge graph in his head rather than cutting a line. It would be fascinating to explore how knowledge management tools can help people do the job of cutting a line through a graph, though that's not really explored in this post. The idea that ought to be central to this post, cutting a line through the knowledge graph, could have been really useful and compelling if not surrounded by trivial complaints. The act of writing notes and being able to search and read notes is useful for anyone, and is essential for those with memory issues. Physical and mental health issues should not be fodder for bad analogies. Particularly disappointing are the references to obesity and hoarding. Yes, being overly focused on the tools used to complete tasks often gets in the way of completing tasks. Yes, network graphs are often boring and gratuitous. Yes, influencers pitching specific methodologies are often full of shit. This is mostly a set of surface-level arguments about superficial aspects of personal knowledge management.
0 kommentar(er)
