summaryrefslogtreecommitdiffstats
path: root/2022/talks/science.md
diff options
context:
space:
mode:
authorSacha Chua <sacha@sachachua.com>2023-02-09 09:07:00 -0500
committerSacha Chua <sacha@sachachua.com>2023-02-09 09:07:00 -0500
commit7580ca9a0a9b2d0238f737244a03a5d1c884377a (patch)
tree145be5cd5f7706c1cc57b54e616b6f59185e67b7 /2022/talks/science.md
parent0b6f11d3c0b8123e051f6065c5437fb34295d6f5 (diff)
downloademacsconf-wiki-7580ca9a0a9b2d0238f737244a03a5d1c884377a.tar.xz
emacsconf-wiki-7580ca9a0a9b2d0238f737244a03a5d1c884377a.zip
add chapters, remove help markers
Diffstat (limited to '2022/talks/science.md')
-rw-r--r--2022/talks/science.md7
1 files changed, 0 insertions, 7 deletions
diff --git a/2022/talks/science.md b/2022/talks/science.md
index f8470d07..b3fc4be9 100644
--- a/2022/talks/science.md
+++ b/2022/talks/science.md
@@ -11,13 +11,6 @@
Vidianos Giannitsis (<mailto:vidianosgiannitsis@gmail.com>)
[[!inline pages="internal(2022/info/science-before)" raw="yes"]]
-[[!template id="help"
-volunteer="sebastian 2022-12-23"
-summary="Q&A could be indexed with chapter markers"
-tags="help_with_chapter_markers"
-message="""The Q&A session for this talk does not have chapter markers yet.
-Would you like to help? See [[help_with_chapter_markers]] for more details. You can use the vidid="science-qanda" if adding the markers to this wiki page, or e-mail your chapter notes to <emacsconf-submit@gnu.org>."""]]
-
Literature notes are a cornerstone of one's zettelkasten. Especially for scientific writing which needs to be based on bibliography, having notes on the literature you read is essential. Inspired by a chapter of "How to Take Smart Notes" by Sonke Ahrens - one of the best Zettelkasten books out there - which talks about the process of writing a scientific article, I crafted a heavily personalized workflow for writing and organizing my literature notes, which I wanted to present to you. Due to university, I have worked on assignments meant to simulate scientific articles and through them I refined this workflow to what it is today, which I am very happy with. I even wrote my own package for addressing part of this workflow, which will be a pivotal part of the talk. I have tried to not overcomplicate the talk, but a familiarity to zettelkasten and scientific writing is expected to get the most out of the talk.