![]() For example, in the Ruby on Rails sub-section, I have a Notion database with the name of the topic, its group, and the level of difficulty. I usually have a "topics and roadmap" sub-section with a description of specific topics related to the programming language. Inside each sub-section (these are actually Notion Pages) I'm taking notes of what I consider to be useful: some basic information that I need to remember, special cases, common problems and their solutions, cheatsheets, etc. ![]() In this section, I have all the information related to the main programming languages I'm learning, as well as related tools, such as Git and GitHub. Complex layouts also don't work too well on mobiles. I tried many other ways of organising my notes, often involving complex Notion databases and relations between notes, or complex multicolumn designs on each Notion Page, but I found that complexity often gets in the way of the ultimate objective: a simple way to insert and extract information. At first, I didn't follow a set structure, but as new concepts came in, I decided to divide my notes into the following parts: When I started studying web development I decided to use Notion as a note-taking system. ![]() Notion ideas code#Notion is my preferred tool to implement a commonplace book for code related knowledge. Notion ideas software#When it comes to software development, having a commonplace book is one of the best things we can do to organise the different coding topics, to keep track of things, and to help not forget concepts. For example, journaling is better done on a dotted physical book, Evernote is better suited to store (and retrieve) PDFs and documents, and Notion is excellent for handling a large amount of data that needs to be interconnected. After having used them all, I found that some of them are better suited for certain kinds of objectives. Learning about these kinds of notebooks pushed me into trying different methods to organise topics I was interested in: from physical notebooks (such as dotted, blank, squared), to digital notebooks (Evernote, OneNote and Notion). Each one is unique to its creator's particular interests but they almost always include passages found in other texts, sometimes accompanied by the compiler's responses. Commonplaces are used by readers, writers, students, and scholars as an aid for remembering useful concepts or facts. Entries are most often organized under subject headings. Such books are similar to scrapbooks filled with items of many kinds: notes, maxims, quotes, letters, tables of weights and measures, and recipes (.). They have been kept from antiquity, and were kept particularly during the Renaissance and in the nineteenth century. Some years ago, looking into something unrelated to programming, I discovered the idea of commonplace books:Ĭommonplace books (or commonplaces) are a way to compile knowledge, usually by writing information into books. ![]() The best solution (so far) I found to cope with all of this is to maintain a commonplace book. I was forgetting things as I learned new ones.too many technologies to keep track of,.I immediately found the following problems: When I first started diving into the web development world I felt overwhelmed by the amount of information out there, and all the topics I wanted to explore and learn. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |