summaryrefslogtreecommitdiffstats
path: root/2024/talks
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--2024/talks.md15
-rw-r--r--2024/talks/learning.md68
-rw-r--r--2024/talks/literate.md50
-rw-r--r--2024/talks/org-teach.md44
-rw-r--r--2024/talks/p-search.md61
-rw-r--r--2024/talks/pgmacs.md49
-rw-r--r--2024/talks/project.md64
-rw-r--r--2024/talks/rust.md34
-rw-r--r--2024/talks/sharing.md39
-rw-r--r--2024/talks/water.md26
-rw-r--r--2024/talks/writing.md34
11 files changed, 484 insertions, 0 deletions
diff --git a/2024/talks.md b/2024/talks.md
new file mode 100644
index 00000000..e642a148
--- /dev/null
+++ b/2024/talks.md
@@ -0,0 +1,15 @@
+[[!meta title="Talks"]]
+[[!meta copyright="Copyright © 2024 Sacha Chua"]]
+[[!sidebar content=""]]
+
+We're getting ready for EmacsConf 2024. Want to propose a talk?
+[[Check out our call for participation|/2024/cfp]] and submit your proposal
+by September 20, 2024 (Friday)!
+
+Here are some of the talks we've accepted so far:
+
+[[!inline pages="internal(2024/schedule-details)" raw="yes"]]
+
+Want to help make EmacsConf even awesomer? [[ [[Volunteer!|/volunteer]]
+
+We hope to see you all around on Dec 7-8 for EmacsConf 2024!
diff --git a/2024/talks/learning.md b/2024/talks/learning.md
new file mode 100644
index 00000000..c5814d23
--- /dev/null
+++ b/2024/talks/learning.md
@@ -0,0 +1,68 @@
+[[!meta title="Survival of the Skillest: Thriving in the Learning Jungle"]]
+[[!meta copyright="Copyright © 2024 Bala Ramadurai"]]
+[[!inline pages="internal(2024/info/learning-nav)" raw="yes"]]
+
+<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing -->
+<!-- You can manually edit this file to update the abstract, add links, etc. --->
+
+
+# Survival of the Skillest: Thriving in the Learning Jungle
+Bala Ramadurai (his/him) - https://balaramadurai.net
+
+[[!inline pages="internal(2024/info/learning-before)" raw="yes"]]
+
+In today's fast-paced world, the need to learn new skills is more crucial
+than ever. The ability to adapt and evolve not only enhances your
+employability but also empowers you to navigate life's challenges more
+effectively. By acquiring new skills, you stay relevant, innovative, and
+capable of seizing opportunities that come your way.
+
+The session will begin with an engaging discussion on the necessity of
+learning new skills, emphasizing that the ability to adapt and evolve is
+crucial. Using the metaphor of "emptying your teacup," you will explore the
+concept of approaching learning with an open mind, ready to absorb new
+knowledge and skills.
+
+Next, you'll dive into actionable techniques for managing your tasks and
+projects efficiently. Bala will introduce the PARA method—Projects, Areas,
+Resources, and Archives—a structured approach to organizing your work and
+life. You will learn how to categorize your tasks, set clear goals, and
+maintain a balanced workflow.
+
+Furthermore, the talk will highlight the importance of regular reviews.
+Weekly, quarterly, and yearly reviews will help you stay on track, reflect
+on your progress, and plan for the future. Through these reviews, you'll be
+encouraged to ask big life questions, such as your financial goals, the
+impact you've had on others, and your work-life balance.
+
+Finally, you'll be introduced to the 9-windows framework, a powerful tool
+for future career planning. Join us and take the first step towards
+mastering the art and developing the mindset of skillful survival in the
+fast-paced ever changing learning jungle.
+
+About the speaker:
+
+Dr. Bala Ramadurai is an author, coach, consultant, podcaster and
+professor. He has authored a book on Design Thinking called Karmic Design
+Thinking (<https://dt.balaramadurai.net>). He has 3 patents to his credit and
+10+ publications in international research journals. He co-founded TRIZ
+Innovation India (<https://trizindia.org>) and is an Adjunct Professor at
+Symbiosis Institute of Business Management (India), Universidad
+Panamericana (Mexico), Symbiosis Institute of Management Studies and
+National Programme on Technology Enhanced Learning (NPTEL). He is also a
+board member in the Board of Studies for Symbiosis International University.
+
+In this talk, you'll discover the importance of continuous skill
+development and learn practical strategies to manage your personal and
+professional growth effectively using Emacs org-mode, Getting Things Done
+(David Allen's GTD), PARA (Tiego Forte's Projects-Areas-Resources-Archives)
+and system operator (or 9-windows). Bala will guide you through a
+transformative journey of self-improvement and productivity.
+
+
+
+[[!inline pages="internal(2024/info/learning-after)" raw="yes"]]
+
+[[!inline pages="internal(2024/info/learning-nav)" raw="yes"]]
+
+
diff --git a/2024/talks/literate.md b/2024/talks/literate.md
new file mode 100644
index 00000000..0fb0a0de
--- /dev/null
+++ b/2024/talks/literate.md
@@ -0,0 +1,50 @@
+[[!meta title="Literate Programming for the 21st Century"]]
+[[!meta copyright="Copyright &copy; 2024 Howard Abrams"]]
+[[!inline pages="internal(2024/info/literate-nav)" raw="yes"]]
+
+<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing -->
+<!-- You can manually edit this file to update the abstract, add links, etc. --->
+
+
+# Literate Programming for the 21st Century
+Howard Abrams (he/him) - @howard@emacs.ch , <https://www.howardism.org>
+
+[[!inline pages="internal(2024/info/literate-before)" raw="yes"]]
+
+Donald Knuth’s idea of *literate programming* in the 80’s and 90’s was
+interesting, but he didn’t realize what Emacs and Org can do in this
+century. In this talk, I would like to go back your initial *dabblings*
+with Org `src` blocks to show how you can program *literately* as quickly
+as you can in any other mode.
+
+Some of the tips and tricks include:
+
+- Automatically keeping your lit code sync’d
+- Easier code generation
+- Jumping to Org headers to help organize code
+- Jumping to code definitions with the xref interface
+
+At the end of this talk, I hope to inspire you to try it again, as my
+personal “go to” is *programming literately*.
+
+I will be following the format and outline in my essay:
+<https://howardism.org/Technical/Emacs/literate-writ-large.html>
+
+About the speaker:
+
+About ten years ago, I gave a talk I called *literate devops* and people
+still ask me if I still use those techniques. For all my personal
+projects, I do. Even projects that I share with others, I often *start*
+programming with an Org file.
+
+I will admit, programming within Org blocks has some burrs, but over
+the years, I’ve filed them off with helper functions, snippets and
+other features. Thought I would share these.
+
+
+
+[[!inline pages="internal(2024/info/literate-after)" raw="yes"]]
+
+[[!inline pages="internal(2024/info/literate-nav)" raw="yes"]]
+
+
diff --git a/2024/talks/org-teach.md b/2024/talks/org-teach.md
new file mode 100644
index 00000000..30b7b8ea
--- /dev/null
+++ b/2024/talks/org-teach.md
@@ -0,0 +1,44 @@
+[[!meta title="org-teach: a minor mode for writing course materials in Emacs"]]
+[[!meta copyright="Copyright &copy; 2024 James Endres Howell"]]
+[[!inline pages="internal(2024/info/org-teach-nav)" raw="yes"]]
+
+<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing -->
+<!-- You can manually edit this file to update the abstract, add links, etc. --->
+
+
+# org-teach: a minor mode for writing course materials in Emacs
+James Endres Howell (he/him) - <mailto:james@endres-howell.org>
+
+[[!inline pages="internal(2024/info/org-teach-before)" raw="yes"]]
+
+I will demonstrate how I used Emacs to produce all the materials for teaching an undergraduate
+molecular and cell biology course at a very large university. My org-teach package
+(<https://git.sr.ht/~jamesendreshowell/org-teach/>) is a collection of Org macros that customize export
+to LaTeX and Beamer in order to produce (1) textbook-style handouts, (2) slides for classroom
+presentation, and (3) quiz and exam questions, all from a single Org source document. It also
+provides a simple minor mode that facilitates authoring such source documents. We will discuss the
+benefits of producing course materials as plain-text outlines, and of exploiting the power of Emacs
+and Org mode for writing and managing book-length teaching materials.
+
+Last year at EmacsConf 2023, I presented some aspects of an earlier version of org-teach
+(<https://git.sr.ht/~jamesendreshowell/org-teach-EmacsConf2023>). This talk will provide more
+background, more details, and some exciting new features.
+
+About the speaker:
+
+James Endres Howell has taught Molecular and Cell
+Biology, Biochemistry, Microbiology, Immunology,
+Toxicology, and Molecular Medicine at Penn State
+since 2006. Recently Dr. Howell has developed
+popular courses for non-science majors in
+Genetics, Ecology and Evolution; Science in
+Literature; and Science in Media. He has used
+Emacs daily since 1988.
+
+
+
+[[!inline pages="internal(2024/info/org-teach-after)" raw="yes"]]
+
+[[!inline pages="internal(2024/info/org-teach-nav)" raw="yes"]]
+
+
diff --git a/2024/talks/p-search.md b/2024/talks/p-search.md
new file mode 100644
index 00000000..01e8aed7
--- /dev/null
+++ b/2024/talks/p-search.md
@@ -0,0 +1,61 @@
+[[!meta title="p-search: a local search engine in Emacs"]]
+[[!meta copyright="Copyright &copy; 2024 Zac Romero"]]
+[[!inline pages="internal(2024/info/p-search-nav)" raw="yes"]]
+
+<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing -->
+<!-- You can manually edit this file to update the abstract, add links, etc. --->
+
+
+# p-search: a local search engine in Emacs
+Zac Romero - <mailto:zacromero@posteo.com>
+
+[[!inline pages="internal(2024/info/p-search-before)" raw="yes"]]
+
+Search is an essential part of any digital work. Despite this
+importance, most tools don't go beyond simple string/regex matching.
+Oftentimes, a user knows more about what they're looking for: who
+authored the file, how often it's modified, as well as search terms that
+the user is only slightly confident exist.
+
+p-search is a search-engine designed to combine the various prior
+knowledge about the search target, presenting it to the user in a
+systematic way. In this talk, I will present this package as well as go
+over the fundamentals of inforation retrieval.
+
+Details:
+
+In this talk, I will go over the p-search. p-search is a search-engine
+to assist users in finding things, with a focus on flexibility and
+customizablity.
+
+The talk will begin by going over concepts from the field of information
+retrieval such as indexing, querying, ranking, and evaluating. This
+will provide the necessary background to describe the workings of
+p-search.
+
+Next, an overview of the p-search package and its features will be
+given. p-search utilizes a probabilistic framework to rank documents
+according to prior beliefs as to what the file is. So for example, a
+user might know for sure that the file contains a particular string,
+might have a strong feeling that it should contain another word, and
+things that some other words it may contain. The user knows the file
+extension, the subdirectory, and has known that a particular person
+works on this file a lot. p-search allows the user to express all of
+these predicates at once, and ranks documents accordingly.
+
+The talk will then progress to discuss assorted topics concerting the
+project, such as design considerations and future directions.
+
+The aim of the talk is to expand the listeners' understanding of search
+as well as inspire creativity concerning the possibilities of search
+tools.
+
+Code: <https://github.com/zkry/p-search>
+
+
+
+[[!inline pages="internal(2024/info/p-search-after)" raw="yes"]]
+
+[[!inline pages="internal(2024/info/p-search-nav)" raw="yes"]]
+
+
diff --git a/2024/talks/pgmacs.md b/2024/talks/pgmacs.md
new file mode 100644
index 00000000..232294ac
--- /dev/null
+++ b/2024/talks/pgmacs.md
@@ -0,0 +1,49 @@
+[[!meta title="PGmacs: browsing and editing PostgreSQL databases from Emacs"]]
+[[!meta copyright="Copyright &copy; 2024 Eric Marsden"]]
+[[!inline pages="internal(2024/info/pgmacs-nav)" raw="yes"]]
+
+<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing -->
+<!-- You can manually edit this file to update the abstract, add links, etc. --->
+
+
+# PGmacs: browsing and editing PostgreSQL databases from Emacs
+Eric Marsden (he/him) - <mailto:eric.marsden@risk-engineering.org>
+
+[[!inline pages="internal(2024/info/pgmacs-before)" raw="yes"]]
+
+PGmacs provides an Emacs-based browsing and
+editing interface for the PostgreSQL DBMS. It
+allows you to browse the contents of database
+tables, in paginated mode for large tables, to
+edit column values in the minibuffer or using a
+widget-based interface, to delete, copy and insert
+new rows, and to save the contents of a table in
+CSV or JSON format. You can run shell commands on
+column values. You can also rename tables and
+columns, add SQL comments, and generate SchemaSpy
+diagrams.
+
+PGmacs works both in the terminal and in GUI mode.
+It uses the pg-el library, which implements the
+PostgreSQL wire protocol, to connect to PostgreSQL
+over the network or over a Unix socket.
+
+The talk will provide an overview of the functionality of PGmacs, then show how it can be easily
+extended to display images stored as database BLOBs inlined in a row-list buffer.
+
+About the speaker:
+
+Eric Marsden developed his first Emacs packages
+pg-el, coffee.el (an implementation of the
+essential Hyper Text Coffee Pot Control Protocol)
+and ipp.el as a procrastination exercise to avoid
+working on his PhD. He continues to use Emacs Lisp
+in his spare time.
+
+
+
+[[!inline pages="internal(2024/info/pgmacs-after)" raw="yes"]]
+
+[[!inline pages="internal(2024/info/pgmacs-nav)" raw="yes"]]
+
+
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 &copy; 2024 Blaine Mooers"]]
+[[!inline pages="internal(2024/info/project-nav)" raw="yes"]]
+
+<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing -->
+<!-- You can manually edit this file to update the abstract, add links, etc. --->
+
+
+# Managing writing project metadata with org-mode
+Blaine Mooers (he/him) - Pronunciation: Blane Moors, <mailto:blaine-mooers@ouhsc.edu>
+
+[[!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/rust.md b/2024/talks/rust.md
new file mode 100644
index 00000000..e994d28f
--- /dev/null
+++ b/2024/talks/rust.md
@@ -0,0 +1,34 @@
+[[!meta title="An Experimental Emacs Core in Rust"]]
+[[!meta copyright="Copyright &copy; 2024 Troy Hinckley"]]
+[[!inline pages="internal(2024/info/rust-nav)" raw="yes"]]
+
+<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing -->
+<!-- You can manually edit this file to update the abstract, add links, etc. --->
+
+
+# An Experimental Emacs Core in Rust
+Troy Hinckley - <https://coredumped.dev>, <mailto:troy@troyhinckley.com>
+
+[[!inline pages="internal(2024/info/rust-before)" raw="yes"]]
+
+An overview and discussion and early prototype of a new Emacs core written in Rust. The talk covers some of the interesting design choices in the GNU Emacs C core, as well as some of the trade-offs made in the Rust core. <https://github.com/CeleritasCelery/rune>
+
+- What is the Emacs core?
+- How has the core evolved?
+- Design trade-offs
+ - multi-threading
+ - Precise GC
+- Being bug compatible with GNU Emacs
+- Comparison
+
+About the speaker:
+
+Hardware Engineer with interest in low-level programming and the hardware-software boundary.
+
+
+
+[[!inline pages="internal(2024/info/rust-after)" raw="yes"]]
+
+[[!inline pages="internal(2024/info/rust-nav)" raw="yes"]]
+
+
diff --git a/2024/talks/sharing.md b/2024/talks/sharing.md
new file mode 100644
index 00000000..4c71a925
--- /dev/null
+++ b/2024/talks/sharing.md
@@ -0,0 +1,39 @@
+[[!meta title="So You Want To Be An Emacs-Fluencer?"]]
+[[!meta copyright="Copyright &copy; 2024 Gopar"]]
+[[!inline pages="internal(2024/info/sharing-nav)" raw="yes"]]
+
+<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing -->
+<!-- You can manually edit this file to update the abstract, add links, etc. --->
+
+
+# So You Want To Be An Emacs-Fluencer?
+Gopar - IRC: gopar, <https://www.youtube.com/@goparism/> , <mailto:gopardaniel@gmail.com>
+
+[[!inline pages="internal(2024/info/sharing-before)" raw="yes"]]
+
+Ever thought about sharing your Emacs knowledge? Starting a YouTube
+channel, blog, podcast, or even smoke signals to share those tidbits? If
+you’ve answered "No", then I'd like to change your mind. And if you said
+"Yes", then you're already on the right path.
+
+In this talk, I will share what I've learned from my journey as an Emacs
+advocate, including tips, setups (both current and past), and various
+alternatives to get your works out there. Most importantly, I'll discuss
+why your story and perspective matter, even if you think otherwise. Your
+unique experience can inspire and help others in the Emacs community.
+
+About the speaker:
+
+Gopar, a fellow Emacs user and advocate, will be sharing insights on how
+everyone can become the Emacs Influencer they never knew they wanted to be.
+
+From starting a YouTube channel to writing blogs, Gopar will provide
+practical tips and share personal experiences to help you embark on your
+journey of sharing Emacs knowledge.
+
+
+[[!inline pages="internal(2024/info/sharing-after)" raw="yes"]]
+
+[[!inline pages="internal(2024/info/sharing-nav)" raw="yes"]]
+
+
diff --git a/2024/talks/water.md b/2024/talks/water.md
new file mode 100644
index 00000000..bd96711c
--- /dev/null
+++ b/2024/talks/water.md
@@ -0,0 +1,26 @@
+[[!meta title="Watering my (digital) plant with Emacs timers"]]
+[[!meta copyright="Copyright &copy; 2024 Christopher Howard"]]
+[[!inline pages="internal(2024/info/water-nav)" raw="yes"]]
+
+<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing -->
+<!-- You can manually edit this file to update the abstract, add links, etc. --->
+
+
+# Watering my (digital) plant with Emacs timers
+Christopher Howard (he/him) - IRC: lispmacs, http://gem.librehacker.com, <mailto:christopher@librehacker.com>
+
+[[!inline pages="internal(2024/info/water-before)" raw="yes"]]
+
+This talk gives a brief introduction to Emacs timer functionality. I explain how I used Emacs timers to water and harvest my flower on the gemini Astrobotany service.
+
+About the speaker:
+
+Christopher Howard is a simulator technican and free software ethusiast living in Fairbanks, Alaska. Christopher explains how he uses Emacs timers to automatically water and harvest his flower on the Astrobotany gemini service.
+
+
+
+[[!inline pages="internal(2024/info/water-after)" raw="yes"]]
+
+[[!inline pages="internal(2024/info/water-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 &copy; 2024 Peter Prevos"]]
+[[!inline pages="internal(2024/info/writing-nav)" raw="yes"]]
+
+<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing -->
+<!-- You can manually edit this file to update the abstract, add links, etc. --->
+
+
+# Emacs Writing Studio
+Peter Prevos (he) - <mailto:peter@prevos.net> , <https://peterprevos.com> , @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"]]
+
+