All Projects → Phantas0s → Alexandria Library

Phantas0s / Alexandria Library

📝 My method to capture, study, and recall interesting knowledge

Projects that are alternatives of or similar to Alexandria Library

Fed Note
我是Mokou, 📘 这里是写前端博客和备忘学习的地方。Vue3 源码解析连载中。喜欢请Star。
Stars: ✭ 180 (+125%)
Mutual labels:  learning, knowledge
Command Line Tools
Awesome Command Line Utilities
Stars: ✭ 201 (+151.25%)
Mutual labels:  learning, knowledge
Knowledge
Everything I know
Stars: ✭ 2,982 (+3627.5%)
Mutual labels:  learning, knowledge
Awesome Vehicle Security And Safety
🚗 A curated list of resources for learning about vehicle security and safety.
Stars: ✭ 59 (-26.25%)
Mutual labels:  learning
Knowledge Base
pdf,txt,djvu, various useful books
Stars: ✭ 63 (-21.25%)
Mutual labels:  knowledge
Op Desafios
Soluções para os desafios (por usuário)
Stars: ✭ 66 (-17.5%)
Mutual labels:  learning
Expo Three Demo
🍎👩‍🏫 Collection of Demos for THREE.js in Expo!
Stars: ✭ 76 (-5%)
Mutual labels:  learning
Learningopencv
Source code for Learning OpenCV 《学习OpenCV》源码及 Mac 运行工程
Stars: ✭ 57 (-28.75%)
Mutual labels:  learning
Lxhive
A lightweight Experience API Learning Record Store (LRS)
Stars: ✭ 73 (-8.75%)
Mutual labels:  learning
Burritos
A collection of Swift Property Wrappers (formerly "Property Delegates")
Stars: ✭ 1,139 (+1323.75%)
Mutual labels:  learning
Frontend Guidelines Zh Cn
本文原文是一篇来自Github上@bendc的6,539星的文章,在此声明,原作者保有所有权利,本文仅供技术探讨学习。
Stars: ✭ 65 (-18.75%)
Mutual labels:  learning
Flexbox30
Learn Flexbox in 30 days with 30 code tidbits ✨
Stars: ✭ 1,127 (+1308.75%)
Mutual labels:  learning
Learn Vim
Vim 实操教程(Learning Vim)Vim practical tutorial.
Stars: ✭ 1,166 (+1357.5%)
Mutual labels:  learning
Building Electron Apps With Js
Materials and code for free course on building Electron app with javascript
Stars: ✭ 62 (-22.5%)
Mutual labels:  learning
Tematres Vocabulary Server
Web application for management formal representations of knowledge, like controlled vocabularies, taxonomies, thesauri and glossaries
Stars: ✭ 73 (-8.75%)
Mutual labels:  knowledge
Estrutura De Dados Em Java
Repositório do Material Estrutura de Dados em Java, contendo os principais tópicos de disciplinas sobre Estrutura de Dados. CURSO SOBRE ED: https://luisaraujo.github.io/Estrutura-de-Dados-em-Java/index.html
Stars: ✭ 58 (-27.5%)
Mutual labels:  learning
Dayasadev
📗 A course to teach non-technical team members what developers do 📗
Stars: ✭ 73 (-8.75%)
Mutual labels:  learning
C koans
C Koans
Stars: ✭ 65 (-18.75%)
Mutual labels:  learning
Learn Aws
☁️ My journey learning Amazon Web Services
Stars: ✭ 65 (-18.75%)
Mutual labels:  learning
Rust In Ten Slides
Short presentations about Rust syntax + concepts
Stars: ✭ 66 (-17.5%)
Mutual labels:  learning

The Alexandria Library

Alexandria Library illustration

count mindmaps Github repo-size

The opportunity before all of us is living up to the dream of the Library of Alexandria and then taking it a step further - universal access to all knowledge. Interestingly, it is now technically doable. -- Brewster Kahle

Welcome to The Alexandria Library!

You'll find here the result of my insatiable thirst of knowledge, mainly in the form of mindmaps (but not only).

How does it look like?

To open the mindmaps, you'll need the software Freemind. It looks like that:

Example of a mindmap

The center is the name of the source. Often, it will be a book, an article, or a video. Then, the first level of branches will be the chapters. Every branch level goes deeper into the knowledge.

What is it for?

As far as I remember, I always liked reading books. Yet, it was difficult for me to recall what I learned in my attempts to share my discoveries. What was the point to read, then?

From there, I tried to find solutions to retain the knowledge of my favorite authors. Some years ago, after experiments and failures, I discovered mindmapping and the fantastic open-source software Freemind.

Quickly, I began to write mindmaps of everything interesting I was reading or watching. These mindmaps (and other resources) constitute now my Alexandria Library.

Why Mindmaps?

Invest regularly in your knowledge portfolio. -- The Pragmatic Programmer

This choice is based on experimentation I've done. I remember more if I create mindmaps of what I'm consuming, and I find it easy to go back to a mindmap to refresh exactly the knowledge I need.

Therefore, it's a personal choice. If you're interested to create a "second brain", you should do some experiments too and see what works for you.

Mindmaps allow me to:

  1. Capture the knowledge fairly quickly, especially because Freemind can be controlled with Vim-like keystrokes. For more information, you can try my Freemind config files.
  2. Mindmaps offer a visual way to access any part of any resource quickly, by localizing the branches I'm interested in.
  3. I can easily add annotations, questions, or even links on a mindmap.

I like trees, I love mindmaps. For me, it's a fun way to capture knowledge. Whatever system you choose, I advise you to use something you like doing, or you won't do it.

Finally, it's way easier to get back to some precise content I previously read or watched using mindmaps, instead of opening a book or a video and trying to localize the content I'm seeking.

My Method To Retain and Capture Knowledge

An investment in knowledge always offer the best interest. -- Benjamin Franklin

It might seems like a lot of work, but I've got pretty effective following this process:

  1. When I read a book or an article which looks interesting, I take detailed notes while reading, on a small notebook. This first phase help me to remember roughly what the content is about.
  2. When I finished the source, I copy my notes into a mindmap. Again, it helps me to transfer the knowledge in my long term memory.
  3. I review my mindmaps once in a while, often depending on my real-life goals. For more abstract knowledge, I refresh them sometimes by testing what I remember. Being able to hide some branches helps a lot. I can as well add questions on the root node, and I try to answer them. My review process can vary grandly depending on the knowledge itself.

The first two points aim to capture the knowledge. The third point helps me to put the knowledge in my long term memory, to be able to use it quickly.

Icons and Meaning

I use icons on some nodes to carry some meaning:

  • Numbers: show the order of reading, which follows the flow of the source material.
  • Green flower: This node expands to an image.
  • Magical wand: example to illustrate the idea, from the source.
  • Key: Personal comment.

Disclaimer

Personal Knowledge

The mindmaps and other resources from this library are tailored to my knowledge and my personality. Therefore, even if I capture content in a detailed way, I can sometimes elude some parts, for different reasons.

Most of the time, I'm trying to avoid these traps:

  • Personal judgments.
  • Understanding mistakes.
  • Biases (especially confirmation bias).

I'm pretty sure there are a ton of them.

Again, because of the personal nature of this library, you'll find some mindmaps hard to read, or even totally obscure. It's not because I think you're stupid (you're not), but because you're not me and, ultimately, I'm not you.

Are we?

My Mindmaps are Just Pale Copies

If you find some mindmaps interesting, I invite you to read (or watch) the original source. You'll get WAY more out of it.

Copyright

If you're the writer of the original content and you don't want me to put online my notes on it, let me know and I will remove them.

Spelling, Syntax, and Grammar

I'm not a native English speaker. Don't be surprised to see many spelling or grammar mistakes in the library, or in this README.

Why Sharing That?

In order to:

  1. Inspire anybody who try to learn and capture knowledge.
  2. Share the content I find interesting, for you to read the original source. My mindmaps can give you an idea of the source.

Questions? Feedback?

I love questions! I love feedback! Don't hesitate to contact me.

Contribution

I won't accept any contribution concerning the content or the organization of my mindmaps.

However, if you have any suggestion to capture or retain knowledge, or if you see any spelling mistakes, feel free to open a pull request.

Licence

Apache Licence 2.0

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].