I have a dedicated couple of pages in a notebook, where I write down the note-taking conventions I use. When transitioning to a new notebook, I would copy those pages, possibly making a few improvements based on past usage. A most unhurried release cycle, if I can say so myself.

Regarding the space management, there are many solutions straight out of the programming world, of course: utilize both sides of the notebook, reserve a minimum number of pages per topic, keep an index with free pages, etc. But there are some hardware ones as well, I'm trying Atoma notebooks (https://atoma.be) these days.

▲

hammock 2 hours ago | parent | next [-]

Would you share your notetaking schemata?

	▲	h45x1 an hour ago \| parent [-]
		Sure. Though to each his own, I'd imagine. Mine is quite basic. - 4 pages at the back are reserved for index. - Daily journal starts at the back. - There is no obligation to have regular entries in the daily journal. - ◦ denotes a past event; ◦ hh:mm denotes an upcoming or past event. - → denotes a task. - "circled" → denotes a completed task. - strikeghrough denotes a cancelled or refiled task. - ¿ optional task, not sure about something ? - "-" is for all types of second-level bullets. (As a side note, I mostly do task organization on the computer, but sometimes in a journal as well.) - Topics start at the front. - Topics are free-form. - A new year starts a new journal. (I don't care for the new year resolutions though. At best, a list of side quests I'd like to do.)

▲

sonicrocketman 3 hours ago | parent | prev [-]

It's basically just designing a dictionary data type. I recall the Python devs talking about a lot of this stuff from the early days.

Everything is related.