Idea
The idea is to make a searchable list of what I have read, viewed , listen, given advice about in past.
This is going to have only technical content, this little book should ideally become better with time. A metric for the book's quality can indirectly also indicate myself becoming a better engineer or it could just be a better reader/scraper of internet, but we will see that in a while (Starting this on a good morning of 10 September 2023, A good checkpointing would be towards the end of the year.)
Making it open for multiple reasons, typically->
- Ignite more curiosity than anything else.
- People stumble upon this and suggest me better ways to learn
- Potentially stumble upon a mis understanding of an article/concept/topic/anything-else and correct me.
- Motivate me to read(more?) or complete the book to the very end(maybe?).
- Can save some time for myself (and readers?) when look at the gist of a certain topic and potentially
ring a bell
in a particularly problematic scenario which otherwise wouldn't have. - Others can also benefit from
- The summaries.
- Ignite more curiosity.
- Find better places to find answers.
Goal
Goal of the book is not to re-write the entire blogs, books(other), transcripts, but rather concise summary of what I learnt and took away from them. In no way it is to dis-respect the original creator of the content or to steal their work. But, in past I have observed it's particularly hard for me to remember things I don't use everyday (but can come handy in certain situations), and this is just an attempt to solve that issue after root causing it to be lack of concise searchability.
Organization
The book is written using mdbook and so, it has a side navigation bar where the specific topic can be searched for and there is a searchable option as well in case the side bar isn't very helpful.
The book will be subcategorized broadly into few sections, and they will have pages (more?) as I keep stumbling more on their respective content.
These are broadly 4 different categories because I feel they are distinct enough in -
- How the content should be consumed
- How they are written and eventually how the summaries of them should be written.
- For example-> A blog is supposed to be pretty short(some exceptions for example-> fasterthanlime but for just that case it can be a subcategory inside articles) as compared to a paper for example.
Hopefully the introduction gets better too, but this is probably all I have as of now.