[[!meta title="Taming things with Org Mode"]]
[[!meta copyright="Copyright © 2023 Gergely Nagy (algernon)"]]
[[!inline pages="internal(2023/info/taming-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. --->
# Taming things with Org Mode
Gergely Nagy (algernon) (he/him) - Pronunciation: "algernon" (all small letters, no capital A, please), IRC: algernon, IRC: algernon (@libera.chat, @OFTC) - but I normally don't check IRC. I'll be around for the conference, but IRC isn't a good way to reach me nowadays. Website: <https://asylum.madhouse-project.org/> Social media: @algernon@trunk.mad-scientist.club (<https://trunk.mad-scientist.club/@algernon>), <mailto:emacsconf@gergo.csillger.hu>
[[!inline pages="internal(2023/info/taming-before)" raw="yes"]]
I'd like to present my solution of taming a NixOS configuration **and** a
Doom Emacs configuration with Org Mode. Taming, as in highlighting the
pain points I had with them, why I found them to be a pain point, and
then offering a solution. Might not be the best solution, but one that
worked out remarkably well for me: writing a lot of words in Org mode to
explain my thinking, for future me, sprinkling some code blocks here and
there, and holistically assembling them into their tangled out form.
Not a very in-depth talk, not a one-size-fits-all kind of solution. The
goal is to show that you don't necessarily have to adapt to languages,
or frameworks. With a little bit of care, and a whole lot of words your
future self will thank you for, you can bend them to your will. So the
computer will work for you, rather than the other way around.
Because Emacs and Org mode can bend time and space - at least in a way,
and you don't even need M-x butterfly!
[[!inline pages="internal(2023/info/taming-after)" raw="yes"]]
[[!inline pages="internal(2023/info/taming-nav)" raw="yes"]]
