I then periodically clump similar content into a single Keep note, usually by simply cut/pasting the relevant links. This happens once every 3-4 weeks.
Now if only Google's Keep team would publish an API...
221–228 of 228 posts
I then periodically clump similar content into a single Keep note, usually by simply cut/pasting the relevant links. This happens once every 3-4 weeks.
Now if only Google's Keep team would publish an API...
Earlier quoted context omitted.
Apologies for the naive question, but how are the native filesystems for metadata storage, like say if you wanted to store Author for a video, or Location for a photo? Do they have preset available fields, or can they store an arbitrary number of key-value pairs?
Well, there are several tag formats, ie Id3v1, Id3v2, Vorbis comments, APE tags, which have have most needed metadata keys already part of the spec and many can add custom pairs.
This is what I learned from designing data architectures: If your data is variegated in format and form, don't look for a single tool/method solution to organize them. There is no single all-purpose organization method. Don't start with figuring out a method to organize your information. You will end up overengineering your org method. Instead, organize your information per "use-case". Start with a specific use-case/…
Earlier quoted context omitted.
Fascinating observation, and could be a corrolary to Nudge theory [1], which won Richard Thaler his Nobel Prize this year, which says Opt-in rather than opt-out is more effective for changing behavior. Underlying idea: friction disincentivizes. [1] https://en.m.wikipedia.org/wiki/Nudge_theory
Yeah, sounds like the same thing. I would not expect you could get a Nobel Prize for that, though. Maybe Scott Alexander should start submitting his articles wherever it is you need to submit them to get a Nobel in economics.
Proving that all the other economists are modeling things wrong is more impressive than you make it sound.
This is what I learned from designing data architectures: If your data is variegated in format and form, don't look for a single tool/method solution to organize them. There is no single all-purpose organization method. Don't start with figuring out a method to organize your information. You will end up overengineering your org method. Instead, organize your information per "use-case". Start with a specific use-case/…
I'm fairly settled on a homebrew style of noguci's system including pen, folded paper in my back pocket, a few paper notebooks as well as markdown, google docs, simplenote (via notational velocity) and google keep.
Here's the post that inspired me towards this system - http://www.literatureandlatte.com/forum/viewtopic.php?p=1592...
However, my system is stunningly poor at filtering and modelling information into memory. I tend to frequently write, bookmark, capture things and leave it at that. That does not help. I have recently begun exploring concepts of spaced repetition to this effect but its too early to comment on this.
I have learnt to differentiate between archive and active areas. Screens and the internet while great at archival, just dont work well for active information that I want to recall at will.
Just wanted to point out that important difference between active and archive information. That link I posted above was from my archival system but remembering Noguci's system and that it applies in this case is from repetition over active information systems.
First, that helps me to rephrase knowledge in my own words (except for quotes, of course), which is good for retaining knowledge.
Second, I use tags and note links that help me to navigate through pieces of knowledge.
Third, I only store files in Dropbox, with a very well-maintained folder structure.
I don't clip stuff in Evernote and don't just copy/paste. I think that bloats the whole thing up and makes it unnavigable.
Earlier quoted context omitted.
Don't start with figuring out a method to organize your information. You will end up overengineering your org method. I think this is an important point. I like to start with a few simple rules: - To retrieve information, I should know where to start: a Schelling point.[0] For me, this is the home page of my wiki. For wenc, it's a Google Doc. - It shouldn't take me more than three clicks to get from my starting point…
What software do you use for your wiki?
if you're using any Unix flavor, activate "locate" and use it. Both do an index of the filenames. So naming correctly your files is important. The 8.3 schema is over now ;)
On a WinPC I also use TotalCommander (of ghisler.com) to make an advanced search (filename and/or content). Of course, find&grep under Unixes do that well!
I got more than 40Gb of ebooks, pdfs, videos, podcasts, etc. in 4 languages (French, English, German, Spanish) and the sole way to find out quickly is global searching.
And constant reorganizing. (With no tool to update, it's a breeze ;))
If you prefer a hierarchical way, then using aliases (symbolic links, on unixes, but since Win7 you can also create links under windoze) can be an alternative to have multiple entries of the same files in your "database" of filenames, making possible to have "NoSQL for dummies" in "RDBMS" as well as "BigData" and "books for beginners" categories.
P.S. I work on documentation systems since 1984. Full text indexing is probably the best solution.
Madmarsu