TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Keep a Log

226 点作者 brunooliv超过 3 年前

46 条评论

ortusdux超过 3 年前
There is a documented phenomenon called the Photo-Taking-Impairment Effect, where taking photos of something can reduce your ability to recall details about it at a later date. It was originally theorized that it was a sort of &#x27;cognitive offloading&#x27;, but further tests have shown that reviewing and deleting the photos does not make up for the deficit.<p><a href="https:&#x2F;&#x2F;www.sciencedirect.com&#x2F;science&#x2F;article&#x2F;abs&#x2F;pii&#x2F;S2211368117301687" rel="nofollow">https:&#x2F;&#x2F;www.sciencedirect.com&#x2F;science&#x2F;article&#x2F;abs&#x2F;pii&#x2F;S22113...</a><p>I remember finishing a complex math test in high school and checking my calculator&#x27;s memory to find that I had done some rather simple single digit multiplication that I had no recollection of. Ever since then I&#x27;ve tried to be conscious of what I offload and what the long term consequences might be. For example, I&#x27;m confident that my ability to spell has decreased as spellcheck technology had advanced.<p>I&#x27;m not recommending against keeping a log. In fact I keep several myself. I use google keep for simple things that I eventually want to forget. I use anki flash cards for spaced repetition study of short concepts that I want to remember. I use oneNote for sprawling interconnected datasets. And lastly, I used waldenpond.press to print and bind stories and articles that I want to remember and revisit.<p>I just think that there is a risk to haphazardly externalizing more and more of your cognition. I started a new carrier 5 years ago, and found that many of my skills had atrophied over the years. I think I spent more time in my first 6 months relearning abilities I had taken for granted 10 years earlier than my new job duties.
评论 #29437607 未加载
评论 #29437271 未加载
评论 #29438384 未加载
评论 #29437981 未加载
评论 #29437636 未加载
评论 #29440824 未加载
评论 #29440684 未加载
评论 #29438523 未加载
pphysch超过 3 年前
I use Obsidian[1] pointing at a local directory of markdown files which is also synced across my devices via Syncthing[2]. Works flawlessly across my various Android&#x2F;Fedora&#x2F;Windows&#x2F;etc devices. Cost: $0.0&#x2F;year.<p>I don&#x27;t really use any Obsidian plugins. Obsidian has good builtin navigation, search, and markdown processing (e.g. LaTeX, code syntax highlighting). It&#x27;s just as easy as opening a new file in $EDITOR, except its a markdown renderer &amp; synced across all my devices.<p>There are also a lot of bells and whistles like graph viz, export to website, etc. that haven&#x27;t gotten in my way.<p>[1] - <a href="https:&#x2F;&#x2F;obsidian.md&#x2F;" rel="nofollow">https:&#x2F;&#x2F;obsidian.md&#x2F;</a><p>[2] - <a href="https:&#x2F;&#x2F;syncthing.net&#x2F;" rel="nofollow">https:&#x2F;&#x2F;syncthing.net&#x2F;</a>
评论 #29443983 未加载
评论 #29437596 未加载
评论 #29439735 未加载
评论 #29436945 未加载
评论 #29437756 未加载
nickjj超过 3 年前
Since about 2001 I used YYYY-MM.txt plain text files and have a shell script to help create notes in the most friendly way I could think of from the command line at <a href="https:&#x2F;&#x2F;github.com&#x2F;nickjj&#x2F;notes" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;nickjj&#x2F;notes</a>.<p>Totally works fine for a knowledge log when you&#x27;re streaming high level details from your brain into text. I still use it today. The repo hasn&#x27;t been updated in 2 years because it&#x27;s a ~20 line script with a simple API that hasn&#x27;t failed yet.<p>But when you want to really go all-in with in-depth notes on 1 semi-broad subject it&#x27;s tricky because in 1 month&#x27;s time if you&#x27;re hardcore deep in the woods of learning, applying and using something you&#x27;re going to end up with hundreds of concepts from an assorted set of tools and it kind of stinks to have all of that info sitting in 1 file. Think about using something like Kubernetes. That&#x27;s really Kubernetes, Kustomize &#x2F; Helm, EKS, various cloud hosting details (networking, etc.), Terraform and ton of super useful commands &#x2F; context. Details you for sure want recorded for later.<p>For this type of info I&#x27;ve been building up a personal knowledge base with <a href="https:&#x2F;&#x2F;obsidian.md&#x2F;" rel="nofollow">https:&#x2F;&#x2F;obsidian.md&#x2F;</a>. It&#x27;s really nice and I highly recommend it. It&#x27;s been working well for keeping things reasonably categorized without wasting a lot of time on the details around keeping links and tags up to date. It also has Vim mode that&#x27;s good enough where day to day writing feels natural.
评论 #29437879 未加载
评论 #29437050 未加载
评论 #29440257 未加载
评论 #29437055 未加载
defenestration超过 3 年前
To retain knowledge and my considerations for my future self and teammembers I create a document before each major task and update it during the task. The headings are: Goal (why are we doing this), Crux (what is the most important consideration, what will make the biggest difference), Current situation (where are we now), Steps (what needs to be done or what is done to reach the goal. The steps can contain specific details on how to get the step done) and Learnings (what did we learn, what are key insights). The files are named YYYY MM DD Taskname. Looking at the directory gives a sense of history. It’s a delight to find a document like this when doing the same task a year later. It also helps to delegate tasks to other teammembers.
评论 #29443107 未加载
ahnberg超过 3 年前
This is such a valuable recommendation. I&#x27;ve been doing the same since 20+ years back. On and off I&#x27;ve been bad at it, but I always end up coming back and continuing.<p>I think of it as more of a daily diary though, I mix random notes of things I&#x27;ve done, thought of doing, or interesting links and&#x2F;or command-lines I&#x27;ve found useful so I don&#x27;t have to reinvent them as often in the future.<p>It has proven to be immensely useful for myself. Can highly recommend!<p>My way is mainly org-mode files through Emacs over the years. Now having switched primarily to VScode I use a simplified org-mode version to get similar feeling, and it works pretty well. Everything is mostly text anyways!
dSebastien超过 3 年前
I agree with this. I tend to remember a lot more when I take time to write things down. It was the way I studied, and is now the main way I learn new things.<p>Writing can take different forms (written words or code), but in both cases, it makes ideas clearer, helps me create mental models, and help me shape my thoughts.<p>I heavily recommend journaling and PKM in general. I recently wrote a few articles on the subject:<p><a href="https:&#x2F;&#x2F;dsebastien.net&#x2F;blog&#x2F;2021-10-07-periodic-journaling-part-1" rel="nofollow">https:&#x2F;&#x2F;dsebastien.net&#x2F;blog&#x2F;2021-10-07-periodic-journaling-p...</a> <a href="https:&#x2F;&#x2F;dsebastien.net&#x2F;blog&#x2F;2021-10-07-periodic-journaling-part-2" rel="nofollow">https:&#x2F;&#x2F;dsebastien.net&#x2F;blog&#x2F;2021-10-07-periodic-journaling-p...</a> <a href="https:&#x2F;&#x2F;dsebastien.net&#x2F;blog&#x2F;2021-12-03-personal-knowledge-management-organization" rel="nofollow">https:&#x2F;&#x2F;dsebastien.net&#x2F;blog&#x2F;2021-12-03-personal-knowledge-ma...</a>
michaelmcdonald超过 3 年前
The author mentions utilizing Slack for this; do so with caution. The free Slack tier only keeps 10,000 messages in history with the added drawback of now your knowledge stash is stored on servers with a 3rd party company rather than files you own &#x2F; control.
评论 #29439348 未加载
评论 #29437333 未加载
decebalus1超过 3 年前
Ah.. time for the monthly note taking generic PKM HN post. Has nobody mentioned Zettelkasten yet? I see org-mode already made an appearance... Either way you go, don&#x27;t forget to self-host!
mtlynch超过 3 年前
I wrote a tool specifically for this, mostly inspired by the Snippets tool at Google. I&#x27;ve been publishing my weekly log in it every week for almost three years:<p><a href="https:&#x2F;&#x2F;whatgotdone.com&#x2F;michael&#x2F;2021-12-03" rel="nofollow">https:&#x2F;&#x2F;whatgotdone.com&#x2F;michael&#x2F;2021-12-03</a><p>The code is all open source if you&#x27;re interested in playing around with it:<p><a href="https:&#x2F;&#x2F;github.com&#x2F;mtlynch&#x2F;whatgotdone" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;mtlynch&#x2F;whatgotdone</a>
joshlemer超过 3 年前
The easiest way to incorporate this into a typical developer&#x27;s workflow is using the vscode-journal plugin: <a href="https:&#x2F;&#x2F;marketplace.visualstudio.com&#x2F;items?itemName=pajoma.vscode-journal" rel="nofollow">https:&#x2F;&#x2F;marketplace.visualstudio.com&#x2F;items?itemName=pajoma.v...</a><p>How it works: From any file, in any project, in VsCode just press CMD + SHIFT + J, select &#x27;Today&#x27; and it will plop you into the journal page for today with today&#x27;s date at the top.
评论 #29437550 未加载
agambrahma超过 3 年前
Churned through a lot of ideas&#x2F;apps for this over time, what works (not &#x27;best&#x27; but &#x27;well enough&#x27;) for me right now is LogSeq.<p>- Daily notes as roots<p>- Local storage<p>- Plain text storage<p>- &quot;wiki-links&quot;<p>- Backlinks and easily traversing notes<p>- Hierarchical format for notes (with folding, so I can &quot;tuck away&quot; a bunch of text and screenshots when I don&#x27;t want to look at them)
评论 #29437567 未加载
jldugger超过 3 年前
Five years ago I decided to buy rocketbook, which I use as a sort of journal. Obvious things go in there, like meeting notes &amp; action items, but also notes from watching conference presentations, weekly Todo list tracking (ala bulletjournal), and outlines for phone calls I need to make (I find the preparation helps with the anxiety of making first phone calls, by collecting important data i might need and key points i need to accomplish ahead of time). I think I prefer the analog nature vs digital notes apps, and the scanner app helps with posterity concerns. Most notes are not that important a year from now! I used to take notes while reading books, but I&#x27;ve since moved that to part two of the system.<p>For things where I absolutely want to remember something, it goes into Anki. While reading books, I make time to go over the chapters and extract key ideas into Cloze deletions. Helps with recall, and the Cloze format helps with recall since you&#x27;re given far more context. And perhaps useful for search.<p>For shell &#x2F; computer stuff, keeping history around helps a lot. In theory important commands could become aliases or functions and kept around via git, but this is more rare.<p>I do have a gnote &#x2F; tomboy setup that I use mostly for long form writing, but that&#x27;s less about journaling experiments &amp; discoveries for later reference and more about getting plans and ideas out of my head so I can stop thinking about them, and drafting the occasional blog post.
beembeem超过 3 年前
My append-only system for *nix, sits in my .bashrc:<p><pre><code> # Open Personal Logfile at end, optionally appending log entry for today if it doesn&#x27;t exist function ed () { local _cur_date _most_recent_date; _cur_date=$(date +%m&#x2F;%d&#x2F;%Y); _most_recent_date=$(grep --color -o -E &quot;^# [0-9]{2}&#x2F;[0-9]{2}&#x2F;[0-9]{4}&quot; ~&#x2F;${LOG_FILE_NAME} | tail -n 1 | cut -d&#x27; &#x27; -f2-); if [[ &quot;${_cur_date}&quot; != &quot;${_most_recent_date}&quot; ]]; then echo -e &quot;\n#\n# ${_cur_date}\n#&quot; &gt;&gt; ~&#x2F;${LOG_FILE_NAME}; echo &quot;Command Comments&quot; &gt;&gt; ~&#x2F;${LOG_FILE_NAME}; printf &quot;%0.s-&quot; {1..81} &gt;&gt; ~&#x2F;${LOG_FILE_NAME}; echo &gt;&gt; ~&#x2F;${LOG_FILE_NAME}; fi; $EDITOR +$(($(wc -l ~&#x2F;${LOG_FILE_NAME} | awk &#x27;{print $1}&#x27;)+1)) ~&#x2F;${LOG_FILE_NAME} } &gt;&gt;&gt; # # 12&#x2F;03&#x2F;2021 # Command Comments --------------------------------------------------------------------------------- &lt;some cmd&gt; # My description of what cmd does, in my own words</code></pre>
评论 #29437183 未加载
simonw超过 3 年前
I&#x27;ve been using GitHub Issues for this for the past few years, and I absolutely love it.<p>Each of my projects has issues. If I&#x27;m fixing a bug or working on a feature I open an issue for it, then I post a stream of comments as I figure out the details, make decisions, find examples of code that I need to use and so on.<p>I have my own private notes repository which I just use for this for things that don&#x27;t relate to a current project and that I don&#x27;t want to publish yet.<p>I add a &quot;research&quot; label to my repos, and open research issues for ideas or for things that I want to explore that are relevant to the project in some way. Recent example: <a href="https:&#x2F;&#x2F;github.com&#x2F;simonw&#x2F;sqlite-utils&#x2F;issues&#x2F;344" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;simonw&#x2F;sqlite-utils&#x2F;issues&#x2F;344</a> - researching STRICT mode that was just added to SQLite, and seeing if it would make sense to support it in my sqlite-utils library.<p>GitHub&#x27;s issues API is comprehensive, so I have a cron that exports all of my issues and comments into a SQLite database that I can access with Datasette. I have a private one with all of my projects, and I also run a public one at <a href="https:&#x2F;&#x2F;github-to-sqlite.dogsheep.net&#x2F;github&#x2F;issues" rel="nofollow">https:&#x2F;&#x2F;github-to-sqlite.dogsheep.net&#x2F;github&#x2F;issues</a> with just the issues from my public Datasette-related projects.<p>I use search against these often. I occasionally even re-discover old notes from Google searches, which include the ones from my public repositories.<p>Many of my issues have dozens of comment replies, all from me. It&#x27;s a great way of keeping a log.
c_o_n_v_e_x超过 3 年前
I’m a product manager and keeping a decision log is a must for me. “Big” decisions &#x2F; major changes getting logged along with the context of how and why the choice was made.<p>Sometimes decisions get revisited and it’s nice to have all of your context, particularly if you are having to defend a choice that was made.
kaetemi超过 3 年前
I&#x27;ve tried wikis, markdown documents, cloud docs, etcetera.<p>Eventually I settled on Word documents, shared over Resilio Sync. It&#x27;s the easiest option to also allow images to be included, and to keep control over my own files. And the desktop and mobile editors are both equally reliable.
评论 #29439563 未加载
adamnemecek超过 3 年前
It’s not writing that’s hard, it’s finding it later, and more importantly remembering that I wrote something down.
评论 #29436919 未加载
评论 #29436849 未加载
_nickwhite超过 3 年前
I used to keep a huge Notepad .txt file of a ton of company knowledge, gotchas, offhand documentation, and any kind of tidbit that I might need later. A few years ago, I migrated all of this to OneNote with detailed, formatted notebooks for every broad subject I could categorize. I recently shared my OneNote notebook with guys relatively new to my team, and I found them using it all_the_time. So not only is the &quot;Knowledge Log&quot; good for you, it can also be a useful tool to help others on your team.
评论 #29437543 未加载
评论 #29437623 未加载
pmulard超过 3 年前
Right now I&#x27;m trying to decide exactly how much information I should store in my knowledge base. There&#x27;s a balance to keeping the base small enough to actually find the information needed and avoid it becoming a huge bloated mess.<p>For example, I keep separate Notion pages for each programming language I use. I also recently started learning Rust and have built up a page that includes even basics like how to declare a variable. The idea was it can exist as a beginner guide and someone can run through it relatively quickly and get a jist for the language.<p>But if I keep using the language, that information may eventually become obsolete (since I&#x27;ll have it memorized) and will probably be a waste of space. Then as I advance through the language, I&#x27;ll want to take note of more advanced concepts and maybe even some specific use cases of problems&#x2F;solutions to code I&#x27;ll have written.<p>I guess that&#x27;s the beauty of editing a knowledge base over time. You can edit it to conform what&#x27;s in currently in your head right now. So maybe in a few years from now, having those simple variable declarations will be a waste of space and I&#x27;ll just want advanced topics covered.<p>Or maybe I&#x27;ll walk away for a few years and need to look up basic syntax again.
评论 #29437497 未加载
abathur超过 3 年前
I find I always fail out of the append-only approach (even though I realize it means I&#x27;m spending more ~orgnizational time&#x2F;energy).<p>I can&#x27;t claim to do it &quot;regularly&quot; in the sense that I do it every day, but I guess I do something like it in that almost every one of my projects has one or more PlainTask documents (i.e., documents that use org-mode-alike PlainTasks extension for Sublime Text).<p>These documents usually start one day as a scratch space to remind me what I was doing before I take a break, or to plan out the next few steps. In any non-trivial project, it&#x27;ll tend to grow to at least a few hundred lines, and almost all of them accrue a top-level section, at the top, titled KNOWLEDGE, where I (my better self, at least) try to record slippery or hard-won technical details I picked up along the way (even if I&#x27;m not smart enough to note them the first time or two I have to bang my head against them).<p>I may not consult most of them again, but they can be a huge help when I get a chance to return to something that I had to back-burner 2 or 3 years earlier, and all of the critical detail has been displaced by newer ephemera...
brunooliv超过 3 年前
Glad to see this has ressonated with so many of you!! Thanks for all the amazing insights in the comments where, as always, a lot of the value lies.
jsguy超过 3 年前
1989 - 2007: notes.txt, 2007 - the future: notes.md
riston超过 3 年前
I am using also similar append only log like for every day, I usually try to write down the flows&#x2F;random ideas&#x2F;doing&#x2F;done items there. I haven&#x27;t brought in a structure overhead so everything is in a single file(couple thousand lines long) plain text file. My main idea is to keep everything sectioned by dates # dd-mm-YYYY # which is really great. I use sublime search and grep which works really great to lookup some older context and commands. Also going back to couple years old notes is really easy and valuable why some of the decisions were made.<p>- KISS
_ink_超过 3 年前
I very often fail in identifying the things that need to be added to the log. List running docker containers? So easy it&#x27;s not necessary to log. That one obscure bug that took days to fix? So many things were tried that didn&#x27;t lead to success, that the path to the solution is not clear anymore.
quartz超过 3 年前
I&#x27;m so deep into Bear Notes that at this point it&#x27;s basically a second brain to me. I used to heavily use tags inside documents for organization but slowly moved away from that and began almost entirely relying on search. The decrease in organizational overhead results in far more &quot;quick jots&quot; and reduces my ability to avoid writing things down because of not wanting to invest in setup time.<p>The only big feature I really wish it had besides non-apple device access (if the bear devs are reading this PLEASE finish the web version!!) is a map view similar to the iOS photos app since it turns out I almost exclusively remember the things I write based on content or location.<p>Interestingly I almost never remember WHEN I wrote something so the timestamps are pretty useless for content recall.
jcun4128超过 3 年前
I&#x27;m still wondering like where should it be. We all carry a phone with us. Seems like adding an extra thing (like earbud holder) sucks... servers &quot;what if it went down&quot;... At the moment I use different combos.<p>I have made a few things, like a url-rest thing that&#x27;s encrytped at rest where the entire website page body is a textarea element. Authenticated and unauth (local) versions. Desktop app. Phone note widget. One I&#x27;m working on is a chrome extension one since I use Chrome everyday.<p>The main thing is it has to be made by me, ego. I used to use One Note but now I&#x27;m scared&#x2F;cringe to look back at my younger self&#x27;s thoughts ha.
orliesaurus超过 3 年前
No one mentions indexing the content as a really important part of logging your notes?
concombre超过 3 年前
I store my TODO list in a markdown file. I edit this with Vim and store this on a git repository.<p>I realized some month ago, that the log is provided for free by git. If I run gitk, I can access all the history of task completion.
评论 #29440195 未加载
mianos超过 3 年前
I use simplenote for this. Mandatory for me is: - synchronisation across multiple machines - synchronisation on android - markdown - reasonable search - sorting by date<p>Over the last few years I have tried many applications for this and many have failed.<p>I really liked boost, but the whole paid&#x2F;free&#x2F;app&#x2F;webapp mess with whole backups disappearing freaked me out.
dukeofdoom超过 3 年前
I started doing this for some software projects I wrote. I created a text file, and every time I fixed an issue, I would make a log entry. Notes what the problem was, what I did and how I fixed it. Since a long time can elapse between bug fixes, I tend to forget how things work. This is super nice to refresh my mind and saves lots of time.
soheil超过 3 年前
&gt; I get free search if I use slack, which is a great upside<p>That&#x27;s a great upside? Any text editor has search. Any text area on any operating system has ctrl+f. I really don&#x27;t understand why sometimes stories like this make it to the frontpage of HN.<p>Yes, keep notes, write down those hard to remember commands somewhere so you can look them up later.
zuj超过 3 年前
I think any sort of memory dump, be it personal or professional is helpful. I used to write the morning pages and got out of habit and trying to get back. More than &quot;cognitive offloading&quot; as others mentioned it helped me in processing the past day. Never tried logging the work related stuff. Will give it a shot.
errcorrectcode超过 3 年前
Revision-controlled wikis are much more organized than some linear information overload or unsearchable paper bullshit.
syngrog66超过 3 年前
summary of the OA: note taking is helpful<p>reaction: agreed. best practice and known as such for a long time<p>I write notes in a plain text file for every project I work on. As I start to see things accumulate around a particular tool, technology or service (or any other common or cross-cutting concern), I eventually carve those note portions out of my per-project notes, clean them up and merge them into a notes file dedicated to that thing.<p>I also look for portions of my notes worth extracting and transforming into executable scripts, complete with variables or templates where makes sense.<p>Plain text notes are also easy to search, version and replicate around. Can upgrade some to Markdown or another structured text format where yields net value. Rinse and repeat.<p>These habits yield increasing ROIs over one&#x27;s life and career.
azaras超过 3 年前
Emacs org-mode is better than Markdown.
评论 #29437098 未加载
fareesh超过 3 年前
What&#x27;s a good tool that:<p>1) Loads in under 5 seconds<p>2) Is searchable, and can hyperlink to other entries<p>3) Syncs across devices
评论 #29441586 未加载
matrixcubed超过 3 年前
I can’t recommend Joplin, synchronized with a cloud storage of your choosing, enough. Markdown, mermaid diagrams, tags, encryption. Everything I need to recall, on every computer I use.
efazati超过 3 年前
I started doing this, since last year. It is brilliant... I don&#x27;t forget anything and easily I can track my stiff<p>The app that I&#x27;m using is Joplin. Open source and you can use it in any platform
rafalbel超过 3 年前
I can relate to that. Without my notes I&#x27;d be lost. Always trying to keep them simple and, if required, to make it accessible to others, to avoid creating tribal knowledge.
Trufa超过 3 年前
I made a dead simple tool today for this purpose to try out svelte:<p><a href="https:&#x2F;&#x2F;dev-logs.netlify.app&#x2F;" rel="nofollow">https:&#x2F;&#x2F;dev-logs.netlify.app&#x2F;</a>
whateveracct超过 3 年前
I have a few GitLab projects I use for this. Some are actual code things, and a couple are just for notes. I make issues all the time along with using the wiki.
darkteflon超过 3 年前
I failed to do this throughout my first career. It’s one of my biggest professional regrets - perhaps the biggest. Reader, don’t be like me.
ms123超过 3 年前
if anyone&#x27;s interested in keeping a public log, i maintain smol.pub.
jsemrau超过 3 年前
I use Evernote for this.
评论 #29437268 未加载
slk500超过 3 年前
emacs org mode
Lhiw超过 3 年前
I keep a daily log of what I work on, i also drop other info links and notes.<p>This is mostly to facilitate daily updates in lieu of stand ups.<p>Another thing I do along side my todo.txt is log important team changes, team switches, people encounters, side projects and any major project milestones that might be useful to point out in my 6 month reviews.<p>It&#x27;s really amazing to search back and find links to things you did months ago when search won&#x27;t pick it up.