From 4d220e0df7b963ba4c17c7b4bb408db936fc939d Mon Sep 17 00:00:00 2001 From: Sacha Chua Date: Sat, 7 Sep 2024 07:32:40 -0400 Subject: add project, writing --- 2024/talks/project.md | 64 +++++++++++++++++++++++++++++++++++++++++++++++++++ 2024/talks/writing.md | 34 +++++++++++++++++++++++++++ 2 files changed, 98 insertions(+) create mode 100644 2024/talks/project.md create mode 100644 2024/talks/writing.md (limited to '2024/talks') diff --git a/2024/talks/project.md b/2024/talks/project.md new file mode 100644 index 00000000..65c33ac1 --- /dev/null +++ b/2024/talks/project.md @@ -0,0 +1,64 @@ +[[!meta title="Managing writing project metadata with org-mode"]] +[[!meta copyright="Copyright © 2024 Blaine Mooers"]] +[[!inline pages="internal(2024/info/project-nav)" raw="yes"]] + + + + + +# Managing writing project metadata with org-mode +Blaine Mooers (he/him) - Pronunciation: Blane Moors, + +[[!inline pages="internal(2024/info/project-before)" raw="yes"]] + +The planning and writing of a scientific manuscript is an intricate process that requires focused effort. +Scientists must make many decisions about what to include and exclude from the paper, often capturing these decisions in notes in the margins, appended notes, or external files. +This ad hoc approach becomes unmanageable when the notes exceed the length of the manuscript, which is often the case. +Nonetheless, these notes can be vital when responding to reviewers' critiques. + +Great scientists like Linus Pauling effectively utilized laboratory notebooks to store metadata on his manuscripts. +His cross-referencing system resembled that of Niklas Luhmann in his physical zettelkasten. +These paper-based approaches have pros and cons, but they are no longer popular because of the hard work required to make them work well. +In comparison, the org-roam-ui view of my zettelkasten provides a garden of endlessly forking paths I can wander in all day. + +I sought a more focused approach to managing my attention and the metadata for one writing project. +I developed a project-specific writing log for this purpose about a decade ago. +The writing log helps me manage anxieties about forgetting where I left off on an interrupted project (Fear of Forgetting, FoF). +In this talk, I will highlight the features of my writing log template in org-mode. + +The first section supports gathering the initial thoughts about the project needed to assemble a central hypothesis around which to build the paper. +Subsections support listing the experiments required to address the central hypothesis and the key discussion points. +These subsections include plans for graphical items like images, data plots, tables, equations, and code blocks. +Of course, this section will evolve as the results accumulate. +When largely completed, this section supports drafting a quarter to a third of a manuscript on day one of the project. + +The following two sections support project administration and assessment. +The administration section includes plans to apply for funding and approvals for the work. +The assessment section supports periodic checks of the project's current state, what holds the manuscript from submission today, and what is missing that makes a larger impact. +This section includes a timeline and milestones to finish the project promptly. +These can be displayed in tables that org-mode so strongly supports. + +The central section of the template contains daily accounts of accomplishments, decisions, and correspondence about the project. +I read this section after a hiatus to resume work on the project quickly. +An open-ended to-do list and a section for collecting ideas for future projects follow the daily log. +The last section contains protocols and guidelines for the various tasks involved in completing the project. + +Here, context switching between the writing log and the manuscript is fine because it usually happens only at the beginning and the end of the writing session. My project-specific approach keeps my mind focused on the project at hand and my FoF under control. +I share my writing log template in org-mode on GitHub. + +About the speaker: + +Blaine Mooers is an associate professor of Biochemistry and Physiology at the University of Oklahoma. +He uses X-ray diffraction to study the molecular structure of proteins and RNAs important in disease. +He writes grant applications, progress reports, manuscripts, lectures, seminars, and talks each year in Emacs. +To control his fear of forgetting (FoF), he uses an external document, the **writing log**, to store metadata about each writing project. +He switched from using LaTeX to Org-mode recently. +He will discuss the features of the writing log and the joys of editing it in Org-mode. + + + +[[!inline pages="internal(2024/info/project-after)" raw="yes"]] + +[[!inline pages="internal(2024/info/project-nav)" raw="yes"]] + + diff --git a/2024/talks/writing.md b/2024/talks/writing.md new file mode 100644 index 00000000..d05af940 --- /dev/null +++ b/2024/talks/writing.md @@ -0,0 +1,34 @@ +[[!meta title="Emacs Writing Studio"]] +[[!meta copyright="Copyright © 2024 Peter Prevos"]] +[[!inline pages="internal(2024/info/writing-nav)" raw="yes"]] + + + + + +# Emacs Writing Studio +Peter Prevos (he) - , , @danderzei@aus.social + +[[!inline pages="internal(2024/info/writing-before)" raw="yes"]] + +Emacs Writing Studio is a comprehensive guide and configuration +for authors using Emacs. The book covers everything from +organising ideas and writing distraction-free to publishing in +multiple formats. The book itself was fully written and published +with the configuration it describes. This talk outlines the proces +of developing this configuration and the book and some +perspectives on using Emacs as a tool to write for humans. + +About the speaker: + +Peter Prevos is a water engineer and social scientist. In this +talk Peter introduces Emacs Writing Studio, a starter kit and +associated manual for authors with no Emacs experience. + + + +[[!inline pages="internal(2024/info/writing-after)" raw="yes"]] + +[[!inline pages="internal(2024/info/writing-nav)" raw="yes"]] + + -- cgit v1.2.3