How to build a second brain as a software developer

386 点作者 PretzelFisch超过 3 年前

62 条评论

judofyr超过 3 年前

I've tried to incorporate some of the ideas of the "second brain" and it didn't really give me that much. My lessons:1. It's always super helpful to write things down. Taking notes from what I read/learn is a great way to verify that I understand it. It sharpens my thinking.2. However, maintaining the "second brain" is a lot work. It's not only about "linking" together notes. You also need to maintain some consistency between them. I ended up spending a lot of time thinking about the structure instead of actually thinking about the content.3. Most of my notes/thoughts fall into two categories: (1) Either they are critical for something I'm actively working on or (2) it's just loose concepts that I'm toying with. For (1) I immediately end up playing with it in code — which is far more concrete and tangible than notes. And for (2) it was rarely important to retain the knowledge accurately many weeks/months later.What I've ended up with is taking a lot of notes, but I hardly focus on organizing them.

评论 #29190262 未加载

评论 #29192355 未加载

评论 #29191363 未加载

评论 #29197733 未加载

评论 #29194889 未加载

评论 #29189898 未加载

评论 #29189710 未加载

评论 #29190212 未加载

评论 #29191276 未加载

评论 #29216460 未加载

评论 #29191284 未加载

forgotmypw17超过 3 年前

I use textfiles...Some are lists, like todo.txtSome are individual topics, brainstorms, etc.For organizing them, I put hashtags like #food inside.Even thousands upon thousands of textfiles (which I'm nowhere near) grep quickly, archive and backup quickly, and transfer to other systems quickly, without lock-in or putting my eggs into someone else's basket.I can even build my own UI on top of it... First, index them into a SQLite, then generate some HTML from it, and have a form which puts another textfile back into the directory. Best of all: the UI never changes without my consent.After getting burned repeatedly by third-party systems with stupid UI changes, data migrations, just plain shutting down, leaking my data, your version is out of date, and your OS is not compatible with our new version, and your device is not compatible with the new OS version, etc., there's no way I'm using a third-party system for this ever again.

评论 #29196489 未加载

评论 #29196457 未加载

评论 #29203124 未加载

评论 #29197738 未加载

评论 #29197026 未加载

评论 #29196692 未加载

评论 #29196789 未加载

评论 #29199082 未加载

mabbo超过 3 年前

I recently read "Getting Things Done"[0] and began incorporating what I learned into my simple second brain. And the results are kind of ridiculously good for me.I built my whole system on a Google Sheet, but I'm experimenting with building myself an App instead- something I would never have been able to accomplish or even been willing to start if I didn't have this second brain helping me.The lessons I've learned from this:1. Being pro-active on things instead of reactive makes everything easier. Each action takes less work because there's no worry or guilt associated with it. Just a small amount of planning to make myself pro-active is a worthy investment.2. Putting things I need to remember into a system and then forgetting about them, trusting that my system has it under control, removes a huge cognitive load from me. I have more energy to use elsewhere.3. Building a system that evolves to fit my needs, being flexible with myself, rather than trying to jam myself into someone else's system has made it work at all. That's why Google Sheets is awesome as a prototype tool for this.[0]<a href="https://gettingthingsdone.com/" rel="nofollow">https://gettingthingsdone.com/</a>

评论 #29198388 未加载

评论 #29192863 未加载

评论 #29196224 未加载

评论 #29200751 未加载

评论 #29199301 未加载

评论 #29194591 未加载

tompark超过 3 年前

Articles like this are nice for picking out ideas to incorporate into your own system. I try to avoid reading much "productivity porn" because it gets repetitive and what captures your attention is the novelty of an idea rather than its effectiveness.There's no system that works for everyone. You have to develop your own, and it will evolve because you change. I started journaling over 10 years ago - it was a simple "daily log" that I only wrote in occasionally. Over time I got more prolific and proficient at it. The structure of that journal became more complex, with different journals for day-job vs personal, multiple levels of summary vs detail planning/notes/ideas, and links between them. I've had to refactor that structure and the taxonomy of tags many times. And much like he describes here, I ended up adding cheatsheets and Q&A and dev templates. *There's no way I'd recommend this system to a beginner.* You have to build your own system according to where you're at in your journey.

评论 #29190606 未加载

spmurrayzzz超过 3 年前

Something that became obvious to me after reading through this is how variant individual learning can be, super interesting to me generally.Very few of the premises used in the article are how I solve problems or gather information as an engineer, either now or in the fledging times of the start of my career 15 years ago. Consequently, the second brain concept seems less useful for me at least at a glance.I thought it was peculiar that in the initial flowchart of "problem requiring information" - there is no mention of RTFS (I use that acronym affectionately here), which is probably the most useful skill I have learned in my time building and maintaining software projects. It may be an innocent omission and its admittedly a steep initial learning curve, but I think it it amortizes incredibly well over the span of a whole career.Not accepting "black magic" anywhere in your stack and challenging yourself to understand why something is breaking can certainly lead to rabbit holes, but avoiding it altogether introduces a significant opportunity cost, in my view.Maybe trying to strike a balance there can dodge the information asymmetry/inefficiency issue established in the premise of the article. Really interesting read, whatever the truth may be.

boffinAudio超过 3 年前

Since 2003 I have printed every single interesting web site I've ever bothered to read - and some I haven't - to PDF file. Instead of Ctrl-D to bookmark, I Ctrl-P to print-to-pdf.I keep these PDF files and use them where most people would have bookmarks.The advantage is that I have an offline cache of materials (60,000+ files), a carefully curated list of stuff I like (or can be bothered to think about long enough to decide I might need it in the future), and endless amounts of material to pdfgrep for further drilling.This has given me quite an edge, time and again, because while others are struggling to find that one bookmark that has the article they kinda remember reading once a few years back, I've already found it, gone to the new site, seen the state of the art as it progressed in the time since my visit, and so on.I believe this has given me a 'second brain'. There is no greater joy than to drop into this directory and do an "ls -alF | grep <some search term>" and find every single page I've read since 2003 on that particular topic, still in the original form I remember - and then to re-visit the page and get the updates.I have a lot of HN articles saved this way - as well as the HN comments too, and this has also served as a second harmonic to my general knowledge, ready and easily accessible should I need it.Try this trick, it really kicks ass!

评论 #29205326 未加载

评论 #29198524 未加载

x0hm超过 3 年前

Lost me here - "Tiago Forte (the original creator of the second brain concept)"Ugh, no. No, no, no. Tiago isn't doing anything original. Tiago has never done anything original. This isn't Tiago's thing.

评论 #29194586 未加载

评论 #29194624 未加载

safog超过 3 年前

Pretty graphs, but I wonder how it stands up to the tests of the real world.I've personally tried to use mind maps (a bit more general than solving technical problems) but gave up pretty quickly. I think part of the problem was the technology itself, mind map apps are mostly desktop only and the mobile experience navigating a 2D diagram is kind of clunky. The other part was just laziness, after building a mind map for an entire weekend I didn't even scratch the surface of what I wanted to achieve with it.Also I take objection to the fact that we go straight to Google for solutions, I check the existing codebase I'm working on, code search in my company's internal repo, code search github, then go to Stackoverflow / docs. So there's some amount of intermediate caching.

评论 #29189642 未加载

评论 #29189237 未加载

评论 #29189090 未加载

评论 #29189221 未加载

评论 #29194645 未加载

throw0101a超过 3 年前

Brings to mind Umberto Echo's "Vegetal and Mineral Memory: The Future of Books" at the Bibliotheca Alexandrina in 2003 (PDF):> WE HAVE THREE TYPES OF MEMORY. The first one is organic, which is the memory made of flesh and blood and the one administrated by our brain. The second is mineral, and in this sense mankind has known two kinds of mineral memory: millennia ago, this was the memory represented by clay tablets and obelisks, pretty well known in this country, on which people carved their texts. However, this second type is also the electronic memory of today's computers, based upon silicon. We have also known another kind of memory, the vegetal one, the one represented by the first papyruses, again well known in this country, and then on books, made of paper.* <a href="https://www.bibalex.org/attachments/english/Vegetal_and_Mineral_Memory.pdf" rel="nofollow">https://www.bibalex.org/attachments/english/Vegetal_and_Mine...</a>

评论 #29191423 未加载

wrs超过 3 年前

I learned about computers and worked in the software industry before nearly all of the boxes on that diagram even existed. This was only 30 years ago! If you needed information you got it from coworkers, source code, vendor documentation, or the library. Of course we had “second brains” to cope, called notebooks and filing cabinets (and notes in text files).It’s kind of sad that instead of using the Internet to vastly expand the reach and effectiveness of that existing system, we seem to have thrown it away so we need articles like this to try to rebuild it. Rather than developing our own thoughts we search for someone else’s thoughts. (And I’m not being holier-than-thou; my first stop is Google and Stack Overflow now too!)

dimal超过 3 年前

Strange that Obsidian was only an honorable mention. For developers, there is no other choice. It has vim mode! My second brain is in Obsidian, and it’s glorious. It’s taken me a while to put enough time into learning things, but now I can see that the power it provides (through plugins and the developer API) is astounding.But it’s interesting to see that he’s using it for completely different things than me. For example, I don’t see much point in saving code snippets.

评论 #29196181 未加载

andrewljohnson超过 3 年前

Nah, he should have stopped with the first diagram.Google plus the internet is your second brain and is the optimal approach for almost everyone. This heavy approach seems like make work that will waste time, and the data will rot, leading to calcified and inaccurate knowledge.

评论 #29191701 未加载

alphadenied超过 3 年前

I didn't see it so I'm recommending it.<a href="https://joplinapp.org/" rel="nofollow">https://joplinapp.org/</a>Use this with the encryption, sync to local filesystem, and with syncthing or similar and you can have an entire "second brain" tree of knowledge written in markdown. On your phone, on your laptop, pc at work, etc.... all for free because devs

dragosbulugean超过 3 年前

All the tools you mentioned are nice.However, none are built for software developers. If you want to know why, ask yourself — does anything here make me feel special as a developer? My guess is the response is "No".I'm the founder of archbee.io, and although it's an early stage product, I built it for engineers — and you can see that by the features: architecture diagrams, GitHub integration, markdown shortcuts, very speedy, API docs with GraphQL and OpenAPI, custom domain hosting, Mermaid diagrams and more.Please check it out and let me know what you thought!:)

评论 #29189872 未加载

tom_wilde超过 3 年前

I recently took on a new, super complex project and can attest to Obsidian beyond useful. I’ve put all notes and info into it, everything.. and it’s really paid off. I now see this process rather like unit testing whereby the structure of the notes mirrors your own thoughts but with a better, searchable memory.

Kaos-Industries超过 3 年前

I don't currently use it so can't comment on what features it has or doesn't have, but I find it interesting that Obsidian [1] is only given an honourable mention in this article when according to the Wayback Machine, its elevator pitch has been "A second brain, for you, forever" since before this article was published.[1] <a href="https://obsidian.md" rel="nofollow">https://obsidian.md</a>

ohduran超过 3 年前

What I miss from these conversations is an emphasis on memory. I know it has a bad rap, since it's not the same as understanding. But I have the feeling that most of our work relies on things that we've done so many times, they've been memorized and do not need to be looked up again.Have a look at Anki <a href="https://apps.ankiweb.net/" rel="nofollow">https://apps.ankiweb.net/</a>, the tool that I use to make memory a choice. See also Michael Nielsen blog on this: <a href="https://augmentingcognition.com/ltm.html" rel="nofollow">https://augmentingcognition.com/ltm.html</a>

abeppu超过 3 年前

I keep seeing articles like this and I keep being a bit disappointed that they mostly adopt techniques that were developed for general knowledge workers ("personal knowledge management system") or ideas by/for writers or researchers, and don't seriously think about how to treat/manage code.A brain isn't just about knowledge; it's also a set of skills, capacities, patterns of behavior. Software is an area it's possible to capture capacities in the form of code that actually does stuff. This article makes brief mention of code snippets, but only really to remark on the kinds of metadata that one should keep to find them later.What I have yet to see a satisfying description of, and what I sometimes try to work towards myself, is a mashup of a library with a knowledge management system, where notes link to code, and both go together in a common repo. However, depending on the kinds of things one stores, the software/library side can stumble over some challenges, and I haven't quite figured out how to keep the overhead spent on maintaining it low. One might have small pieces of code in many languages, or different versions of the same language (e.g. making notes about macros in scala 2.x vs scala 3), and notes made at different times might incidentally become dependent on differing specific versions of library (e.g. ideas in statistical analysis that use pandas).

评论 #29193059 未加载

评论 #29194579 未加载

infogulch超过 3 年前

> These categories are all nested. Tasks are nested under Projects which fall under Areas which fall under Resources, with Archives serving as the catch-all category.This does not match my understanding of PARA as described by Tiago. [0] These are not a straight-line "flat" nesting, there's some branches. Areas are at the top, they represent responsibilities, have a broad scope, and undefined/unknowable end date. Both Projects and Resources are nested under an Area. Resources are tools or provisions or information that are potentially useful to fulfill the Area's responsibility. Projects are an attempt to take a little bite out of the Area's responsibility by considering a particular goal in a narrow time horizon. You should be able to use the Area's Resources to help complete a Project.Archives are the category that is not like the others. It's more of a "completed" / "abandoned" status that can be applied to any of the other three as a way to sift out things that are no longer immediately relevant without deleting them. I like to think of this as a generic, orthogonal Time dimension. Maybe infogulch's version would be called PAR/T.[0]: I found the Building a Second Brain podcast does a pretty good job of outlining these categories more clearly. Episodes are short ~8m and digestible. <a href="https://fortelabs.co/blog/basbpodcast" rel="nofollow">https://fortelabs.co/blog/basbpodcast</a>

genghisjahn超过 3 年前

My second brain keeps moving. For example, I have a great setup with Notability on an iPad. Except after a few months, I start typing stuff into Workflowy. No reason, I just reach for a different tool. A few months later I'm in a random text file and then back to Notability. I don't know why I do this. One thing that sorta helps is implementing the Jonny Decimal System so that all the different pieces can be indexed. But, I make it harder than it needs to be.

评论 #29194450 未加载

评论 #29192288 未加载

评论 #29191737 未加载

评论 #29189804 未加载

评论 #29189837 未加载

thrower123超过 3 年前

My second brain is the 400 browser tabs that I have open

评论 #29189453 未加载

评论 #29189533 未加载

cpb超过 3 年前

Having tuned in a few times to watch <a href="https://twitter.com/AdamLearnsLive" rel="nofollow">https://twitter.com/AdamLearnsLive</a> on twitch, I was inspired to take notes throughout my development process. What I noticed of Adam13531's note taking was they wrote down every question that came to mind as they worked down the rabbithole of learning that is software development.For my own practices, I've added in a bit of an OODA loop process. My intent is to systematically balance between deciding and executing, focusing on accumulating knowledge towards achieving a goal.When I'm stuck, or dealing with unknowns, the brainstorming in each of Observe, Orient and Decide enable me to gain some flow.Later, I can observe where I had blindspots, or anchored to certain contexts or scopes. I'm noticing I could develop checklists to go through to avoid repeating those biases.

评论 #29190236 未加载

Cthulhu_超过 3 年前

It sounds like a lot of work and overhead for something that nine times out of ten I'll only need once and if I need it again, I'll default to Google anyway.What good is doing all this filing and organizing if it only serves you personally? It's like building and maintaining a cache, but with a high percentage of cache misses.

评论 #29210128 未加载

tconfrey超过 3 年前

This seems too heavyweight to me, specifically step 3 with all the data structures and templates. There's just no way capturing all that metadata is going to pay off for me. I see it as:1) define your basic structure for capture (I also like PARA[1])2) invest in the tools (for me, emacs/org-mode combined with the BrainTool browser extension - disclosure I built it[2])3) understand your inflows and workflow.4) just use search on your second brain for retrieval.[1] <a href="https://fortelabs.co/blog/para/" rel="nofollow">https://fortelabs.co/blog/para/</a>[2] <a href="https://braintool.org/2021/05/15/Organizing-your-life-with-a-Topic-Manager.html" rel="nofollow">https://braintool.org/2021/05/15/Organizing-your-life-with-a...</a>

jiggunjer超过 3 年前

I find I have an itch to create lists. Once I've made the list (knowing it's useless) it gets archived; the itch has been scratched and I go on with my day.Stuff like this isn't really a second brain. It's a stick for scratching.

评论 #29195208 未加载

johnnylambada超过 3 年前

I have a simple system. For every “project” I’m involved in i make a new Google folder and at the top of it i make a notes doc. The document has a table at the top filled with pertinent information about the project, and then just below that I take notes for every day. Every day that I work on that project at least. Yesterdays notes get pushed below today’s notes and I just move forward like that. I just search Google docs for keywords and find them in my notes from days weeks or months ago. The nice thing about Google docs as I can take screen captures and just stuff them in the doc

MrZongle2超过 3 年前

I was disappointed that Joplin (<a href="https://joplinapp.org/" rel="nofollow">https://joplinapp.org/</a>) wasn't included in the app list.Having used both Evernote and OneNote, I've found Joplin to be a better choice, especially when I'm bouncing between platforms. It doesn't lock you to a particular ecosystem or cloud service, and the open source app is free for use.For what it's worth, I'm not affiliated with Joplin, I'm just a user.

评论 #29202437 未加载

评论 #29191881 未加载

dd444fgdfg超过 3 年前

I've always done something similar, but less structured and probably with less intent.Most of the problems we software developers encounter, we've solved before. So it's usually a case of recognizing the pattern of problems this is, and matching it to one you've solved before, and quickly being able to reference that previous solution. That's 95% of getting it done.

robofanatic超过 3 年前

time required to curate a local pantry of information is just too high and mostly benefits decline overtime unless that information is very complex to remember and so specific to your domain that you wont find a quick solution online.IMO Search Engine is the food pantry. local knowledge repositories are good for any domain specific knowledge thats really hard to find elsewhere online

评论 #29189755 未加载

DeathArrow超过 3 年前

I cam across two alternatives for Roam Research:Foam. Built on Visual Studio Code and GitHub, Foam is early but already powerful. Write your content in markdown, use [[page]] for internal links, and explore your content with an interactive graph. The Backlinks Explorer lets you find all notes that link to a specific note. Foam also makes it easy to back up your notes on GitHub. [1]Athens. Quite ambitious, Athens aims to offer a full open-source version of Roam. Built with Clojure. It's founder wanted to work for Roam but was rejected because he didn't know Clojure. So he learned Clojure and started writing an open source alternative. Roam was rejected by YC but AThens was accepted. [2][1] <a href="https://foambubble.github.io/foam/" rel="nofollow">https://foambubble.github.io/foam/</a>[2] <a href="https://github.com/athensresearch/athens" rel="nofollow">https://github.com/athensresearch/athens</a>

mgdv超过 3 年前

I've used lots of 'note' apps but ended up with 2 parts that work for me 1. A physical notebook for quick capture 2. A single markdown document which I search through or edit with VimI have simple vim macro that prints today's date bound to a key. This makes it easy to write notes for that day. It's worked well for the last few years

评论 #29191512 未加载

spdegabrielle超过 3 年前

<a href="https://tiddlywiki.com/" rel="nofollow">https://tiddlywiki.com/</a> This has been solved

drughunta超过 3 年前

logseq (<a href="https://github.com/logseq/logseq" rel="nofollow">https://github.com/logseq/logseq</a>) has all features of roam plus- it's free - markdown (or orgmode) based local first - open source - PDF annotator (fantastic for scientific papers) - Built in spaced repetition - very fastCan highly recommend it

razzimatazz超过 3 年前

I would like to hear people's thoughts on how to coach a junior on how to get a 'second brain' (new term for me) going. Plenty of your average new developers won't have the experience to build it on their own, or maybe they just wont know what the topics and projects are that they will be working with.

评论 #29210219 未加载

ukoki超过 3 年前

I feel like improving my note taking has helped me continue improving my development speed and quality when it was at risk of stagnating. Not by way of documentation (which I do use it for) but more for tracking multiple streams of work in multiple levels of detail.I keep a highly nested todo list of things I'm currently working on where I can track incoming tasks ("reply to Bob about XYZ") as well as split current work into subtasks ("don't forget to add a test for edge case ABC"). I find the splitting really helpful because as you dive into a complex piece of code that you want to change or add a feature to you will "see things on the way down" that need updating but updating them is blocked on _other_ changes you need to make. A todo list helps track all of this stuff and ensure it does not get forgotten.

SubiculumCode超过 3 年前

2nd brain = 2nd job.Here is my flow. Google. If its really good/unique and I am afraid that I won't find it again, then I bookmark it, and if I think it will actually disappear from the internet, then I will scrape the content for a 2nd brain.Now whether Google is best depends. Sometimes specialty engines would be better.

Olreich超过 3 年前

The best approach is to not build a knowledge management system for yourself until you need it. When you've forgotten something you need a few times, maybe it's time to set up a "common notes" file that you can check first for those things that won't stick. Then when that gets unwieldy, maybe split it into a folder of organized notes with a grep or fuzzy search in front of it (or one of those note-taking apps). When that stops working for you, pull out bigger guns and build something that works specifically for how you use it.By waiting until you actually need it, you skip a lot of the work in maintaining a knowledge base you don't use, and you only build out the bits you actually need, instead of wasting a bunch of effort on things that sound nice, but won't actually help.

piokoch超过 3 年前

I read all those note taking threads with great passion (from the first to the last comment - typically comments are way more interesting then articles), looking for the holy grail of note taking.I've tried a lot of solutions but the one that clicked for me is a mixture of org-mode for current/smaller notes and Zettlr (<a href="https://www.zettlr.com/" rel="nofollow">https://www.zettlr.com/</a>) for stuff that my kids will inherit one day.Zettlr's advantage is that is it just a layer on top of folder or folders with standard markdown files. Zettlr adds ability to tag and search notes plus it displays MD in a nice way. Nothing more, nothing less.I keep the notes on Synology drive, so they are synced/backed-up and it just works.

jmnicolas超过 3 年前

Frankly I think it's completely irrelevant for us developers: our field is evolving so fast that whatever you store now in your second brain will probably be obsolete by next year.Basically it's like advocating for old school paper encyclopedia in the age of Google.I fail to see what is so inefficient with a web search as a second brain: the content is always up to date and you have a chance of stumbling upon something that is better than what would be stored in your second brain.And let's not forget about that maintaining a second brain is a real time sink.The only plus side of a local second brain is that it's functional without an internet connection, but can you really write software in good conditions without an internet access (I sure can't)?

评论 #29210253 未加载

nenadst超过 3 年前

Missing from the list is Zettlr <a href="https://zettlr.com/" rel="nofollow">https://zettlr.com/</a> which is opensource, looks very nice and is built for the Zettelkasten method and has LaTeX integration.Was quite useful for some university classes.

skobovm超过 3 年前

I think that ultimately a “second brain” system belongs at the OS level — as opposed to application — as it can greatly reduce friction from an interaction standpoint (e.g. double click iPhone power button to access your “brain” as opposed to pulling up a NFC credit card). I even went as far as getting the system concept patented while at Microsoft some years back: <a href="https://patents.google.com/patent/US20180349497A1/en" rel="nofollow">https://patents.google.com/patent/US20180349497A1/en</a>

spiderice超过 3 年前

> These categories are all nested. Tasks are nested under Projects which fall under Areas which fall under Resources, with Archives serving as the catch-all category.This article got me reading about PARA. But it seems like this sentence is very much the opposite of what the creator of PARA says to do. Sounds like there shouldn't be any nesting of categories: <a href="https://fortelabs.co/blog/p-a-r-a-ii-operations-manual/" rel="nofollow">https://fortelabs.co/blog/p-a-r-a-ii-operations-manual/</a>

Trixter超过 3 年前

I'm active in the vintage personal computing space, and I find it funny when this topic crops up every decade or so under a different name. In the 1980s, there was a entire software category of "personal knowledge management systems" where each product claimed it had the best system. "Second brain" is no different; it's a group of concepts that may or may not work for you, but as these comments show, they certainly don't work for everyone.

6510超过 3 年前

Make a blog, consider your future self the most stubborn and unreasonable audience possible and convince yourself you did a terrible job living up to the expectations. This guy is always elaborating on the obvious and skipping just those much needed details you were looking for.The only thing I got right was to title creative outburst with strings of random characters created by slapping the keyboard. You should just open some of those from time to time just to see what is inside.

akouri超过 3 年前

I am constantly getting flummoxed by the PARA system. It ends up taking me more time trying to figure out the nuanced rules on where to put something (Projects/Areas and Areas/Resources are the most persnickety ones) that I often end up duplicating a concept and having two folders for it, one in each hierarchy. I'm still not sold on the PARA organizational method, but maybe there's something I'm missing.

评论 #29194748 未加载

评论 #29194232 未加载

评论 #29194554 未加载

jacksonkmarley超过 3 年前

I liked the premise of this article, but I didn't see much use for anything after it started talking about how to achieve it....Except the 'personal stack overflow ' idea. Because so many of the answers to my questions are there, or in rando blog posts, having a personal SO full of actual SO answers (that I found useful) would actually be pretty good. Then a personal Google to search it and I'd be most of the way there.

fastball超过 3 年前

I am the co-founder of one of the honorable mentions in the list of viable software (Supernotes), happy to answer any questions people might have!

going_to_800超过 3 年前

You guys should try Fibery.io

评论 #29193789 未加载

emrah超过 3 年前

Searching anew (instead of using one's own cache of previous finds) is still valuable because you may discover better results, or new results that may lead to new/better thinking, or the answer to your question might have changed since the last time you searched.If i can't find any of these, then falling back on previous finds is valuable.

clueless123超过 3 年前

Been using mindmaps to keep "knowledge" for years (freemind) best thing ever.The older I get, the more useful they become.

Sophistifunk超过 3 年前

None of these options presented are any good because you can't easily (or at all in most cases) program them.

评论 #29197116 未加载

jhylands超过 3 年前

Grepper? <a href="https://chrome.google.com/webstore/detail/grepper/amaaokahonnfjjemodnpmeenfpnnbkco?hl=en" rel="nofollow">https://chrome.google.com/webstore/detail/grepper/amaaokahon...</a>

kzrdude超过 3 年前

I'm trying some stuff, sure.I'm wondering how to keep "slices of projects" aligned. Like, different things are in different repos - how to keep notes and additional files belonging to that, it ends up being a side hierarchy?

habeebtc超过 3 年前

This perfectly captures how I use ADO wiki.I am considered to be super-together by my colleagues. I am confident if they have to pick up my work, they can data mine what they need from the few hundred pages I have produced to date.

ziggus超过 3 年前

Related: <a href="https://news.ycombinator.com/item?id=22276184" rel="nofollow">https://news.ycombinator.com/item?id=22276184</a>

foolinaround超过 3 年前

the author does not get deep into when/what to put into the 'second brain'.Just like one does not go to the market unless it is not in the pantry, one should not replicate what google can get for you in a second.So, then, what needs to be in the second brain is more of keywords and categories, so that we can make the google searches more effective for the particular question we haveP.S.: assuming we will always have google/some search engine.

评论 #29217263 未加载

betwixthewires超过 3 年前

While these are great concepts, I find it to be an overcomplication for my needs. When we build systems of any kind it's nice to imagine the ways in which they make our lives easier, and we always underestimate the required maintenance of our systems and the ways in which they come to constrain our thinking and action.I have a pretty simple organizational structure for information: I keep text files on ongoing projects and ideas. I think on ones that are on the back burner and update my notes on them when I have something compelling come to mind, and the forefront ones or ones that are related to maintenance I keep accessible, usually on my desktop or always open in my text editor. It's a bit of a disorganized system but it is just the right level of complexity. I'm the kind of person who knows which pair of pants on the floor that I left my wallet under last night and so a good portion of organization exists in my head and I work better that way. I'm always on the lookout for new organizational tools, but a huge criteria for them is that they require little to no overhead or maintenance.I do rely on online search a little too much, I often forget to store information I find and might need later and instead store my google-fu queries in my head, and because of that often times I cannot find it again later (because online search as a tool is degrading as we speak) and this article is a good reminder that I cannot rely on external tools like that that I have no say in them continuing to work the same way.

Havoc超过 3 年前

Not sure about second brain but I’ve come to the conclusion that a life long git repo is probably a good idea. eg keeping track of vaccines, medical history etc.

评论 #29215937 未加载

Im_your_dada超过 3 年前

Build a second brain to enrich the company you work for?

评论 #29189001 未加载

评论 #29189193 未加载

评论 #29190571 未加载

firemelt超过 3 年前

I use gist and my last projects repo

tehjoker超过 3 年前

Sounds like a laboratory notebook.

vishnugupta超过 3 年前

tl;dr make a habit of systematically documenting. Use a good tool such as Roam Research (I use it and recommend)