<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>orgmode &amp;mdash; Kemal&#39;s Braindump</title>
    <link>https://write.moxnet.eu/tag:orgmode</link>
    <description>Rambling thoughts and reflections</description>
    <pubDate>Thu, 16 Apr 2026 08:33:37 +0200</pubDate>
    <item>
      <title>Brainiac v1.1 released</title>
      <link>https://write.moxnet.eu/brainiac-v1-1-released</link>
      <description>&lt;![CDATA[Brainiac v1.1 released&#xA;&#xA;#emacs #orgmode #brainiac #gtd #productivity&#xA;&#xA;Brainiac is a minimal, distraction-free Emacs configuration designed for GTD workflows, notes, and task management using Org-mode. This v1.1 update focuses on stability and workflow refinements — keeping the setup lightweight while improving daily use.&#xA;&#xA;If you&#39;re new to Brainiac, check out the original introduction to learn about the philosophy behind this configuration.&#xA;&#xA;!--more--&#xA;&#xA;For the past four months, Brainiac has been my daily Emacs setup for managing work projects, personal tasks, notes, and planning. I’m genuinely impressed by how little needed to change — proof that a simple Emacs workflow can stay effective without constant tweaking.&#xA;&#xA;✅ What’s New in v1.1&#xA;&#xA;Default search now uses rgrep instead of find-grep-dired&#xA;Added ultra-scroll for smoother scrolling over large images&#xA;Removed DONE tasks from agenda to reduce clutter&#xA;New focused Day Agenda:&#xA;&#xA;  Scheduled tasks, deadlines, and priority backlog ([#A])&#xA;New Week Agenda:&#xA;&#xA;  Full week view + entire backlog to support weekly review flow&#xA;Statistic cookies auto-update on save (accurate project status always)&#xA;Improved print CSS to prevent long lines from overflowing&#xA;&#xA;Along with the update, you’ll now find a picture of Brainiac — a friendly organization-loving robot — in the config folder. Enjoy the company!&#xA;&#xA;Get your update from here.&#xA;&#xA;br&#xD;&#xA;- -&#xD;&#xA;&#xD;&#xA;Have any thoughts or comments?]]&gt;</description>
      <content:encoded><![CDATA[<h2 id="brainiac-v1-1-released" id="brainiac-v1-1-released">Brainiac v1.1 released</h2>

<p><a href="https://write.moxnet.eu/tag:emacs" class="hashtag"><span>#</span><span class="p-category">emacs</span></a> <a href="https://write.moxnet.eu/tag:orgmode" class="hashtag"><span>#</span><span class="p-category">orgmode</span></a> <a href="https://write.moxnet.eu/tag:brainiac" class="hashtag"><span>#</span><span class="p-category">brainiac</span></a> <a href="https://write.moxnet.eu/tag:gtd" class="hashtag"><span>#</span><span class="p-category">gtd</span></a> <a href="https://write.moxnet.eu/tag:productivity" class="hashtag"><span>#</span><span class="p-category">productivity</span></a></p>

<p>Brainiac is a minimal, distraction-free Emacs configuration designed for GTD workflows, notes, and task management using Org-mode. This v1.1 update focuses on stability and workflow refinements — keeping the setup lightweight while improving daily use.</p>

<p>If you&#39;re new to Brainiac, check out the <a href="https://write.moxnet.eu/brainiac-v1-0-released">original introduction</a> to learn about the philosophy behind this configuration.</p>



<p>For the past four months, Brainiac has been my daily Emacs setup for managing work projects, personal tasks, notes, and planning. I’m genuinely impressed by how little needed to change — proof that a simple Emacs workflow can stay effective without constant tweaking.</p>

<h2 id="what-s-new-in-v1-1" id="what-s-new-in-v1-1">✅ What’s New in v1.1</h2>
<ul><li>Default search now uses <code>rgrep</code> instead of <code>find-grep-dired</code></li>
<li>Added <code>ultra-scroll</code> for smoother scrolling over large images</li>
<li>Removed <code>DONE</code> tasks from agenda to reduce clutter</li>

<li><p>New focused <strong>Day Agenda</strong>:</p>
<ul><li>Scheduled tasks, deadlines, and priority backlog (<code>[#A]</code>)</li></ul></li>

<li><p>New <strong>Week Agenda</strong>:</p>
<ul><li>Full week view + entire backlog to support weekly review flow</li></ul></li>

<li><p>Statistic cookies auto-update on save (accurate project status always)</p></li>

<li><p>Improved print CSS to prevent long lines from overflowing</p></li></ul>

<p>Along with the update, you’ll now find a picture of Brainiac — a friendly organization-loving robot — in the <code>config</code> folder. Enjoy the company!</p>

<p>Get your update from <a href="https://moxnet.eu/s/FbYfjRy2ojoR9kp">here</a>.</p>

<p><br></p>

<hr>

<p><em>Have any <a href="mailto:kemal@moxnet.eu">thoughts or comments</a>?</em></p>
]]></content:encoded>
      <guid>https://write.moxnet.eu/brainiac-v1-1-released</guid>
      <pubDate>Tue, 04 Nov 2025 20:12:30 +0100</pubDate>
    </item>
    <item>
      <title>Announcing Brainiac Project</title>
      <link>https://write.moxnet.eu/announcing-brainiac-project</link>
      <description>&lt;![CDATA[#emacscarnival202506 #brainiac&#xA;&#xA;Somewhere during the COVID pandemic I started checking out #emacs, because of a talk I saw on #orgmode that tickled my curiosity.&#xA;&#xA;!--more--&#xA;&#xA;In the beginning I didn&#39;t dig into the manuals, as you should do, but started using the editor directly and customized stuff by integrating code snippets from different posts and blogs I stumbled upon, while looking for solutions for problems I faced.&#xA;&#xA;Over the years as my proficiency grew, so did my Emacs config. Although I regularly removed packages I didn&#39;t use, at some point in time I did task management, note taking, blogging, news reading etc. with Emacs and kept on bringing in new packages into the mix.&#xA;I didn&#39;t really reach the state of bankcruptcy, but I gathered some #elisp snippets I didn&#39;t understand or simply didn&#39;t remember why I got them at all.&#xA;&#xA;So in order to force myself to finally start reading the manuals and to learn some proper Elisp, I started hacking on a new configuration for #emacs ... as this is what you do as an Emacs user.&#xA;&#xA;The goal of the Brainiac configuration is to minimize the configuration to the bare minimum I need (e.g. tasks and notes) and try to stick to the built-in packages as much as possible. If I need something extra, I would try to implement it myself.&#xA;&#xA;You can follow how the configuration progresses here: Brainiac.&#xA;It is already fully functional and I am using it daily for private and work related stuff. When it reaches v1.0, I will write about my workflow that defined the configuration.&#xA;&#xA;br&#xD;&#xA;- -&#xD;&#xA;&#xD;&#xA;Have any thoughts or comments?]]&gt;</description>
      <content:encoded><![CDATA[<p><a href="https://write.moxnet.eu/tag:emacscarnival202506" class="hashtag"><span>#</span><span class="p-category">emacscarnival202506</span></a> <a href="https://write.moxnet.eu/tag:brainiac" class="hashtag"><span>#</span><span class="p-category">brainiac</span></a></p>

<p>Somewhere during the COVID pandemic I started checking out <a href="https://write.moxnet.eu/tag:emacs" class="hashtag"><span>#</span><span class="p-category">emacs</span></a>, because of a talk I saw on <a href="https://write.moxnet.eu/tag:orgmode" class="hashtag"><span>#</span><span class="p-category">orgmode</span></a> that tickled my curiosity.</p>



<p>In the beginning I didn&#39;t dig into the manuals, as you should do, but started using the editor directly and customized stuff by integrating code snippets from different posts and blogs I stumbled upon, while looking for solutions for problems I faced.</p>

<p>Over the years as my proficiency grew, so did my Emacs config. Although I regularly removed packages I didn&#39;t use, at some point in time I did task management, note taking, blogging, news reading etc. with Emacs and kept on bringing in new packages into the mix.
I didn&#39;t really reach the state of <a href="https://www.emacswiki.org/emacs/DotEmacsBankruptcy">bankcruptcy</a>, but I gathered some <a href="https://write.moxnet.eu/tag:elisp" class="hashtag"><span>#</span><span class="p-category">elisp</span></a> snippets I didn&#39;t understand or simply didn&#39;t remember why I got them at all.</p>

<p>So in order to force myself to finally start reading the manuals and to learn some proper Elisp, I started hacking on a new configuration for <a href="https://write.moxnet.eu/tag:emacs" class="hashtag"><span>#</span><span class="p-category">emacs</span></a> ... as this is what you do as an Emacs user.</p>

<p>The goal of the <em>Brainiac</em> configuration is to minimize the configuration to the bare minimum I need (e.g. tasks and notes) and try to stick to the built-in packages as much as possible. If I need something extra, I would try to implement it myself.</p>

<p>You can follow how the configuration progresses here: <a href="https://moxnet.eu/s/D5ZCNJwrwFjf8LY">Brainiac</a>.
It is already fully functional and I am using it daily for private and work related stuff. When it reaches v1.0, I will write about my workflow that defined the configuration.</p>

<p><br></p>

<hr>

<p><em>Have any <a href="mailto:kemal@moxnet.eu">thoughts or comments</a>?</em></p>
]]></content:encoded>
      <guid>https://write.moxnet.eu/announcing-brainiac-project</guid>
      <pubDate>Sun, 08 Jun 2025 23:44:53 +0200</pubDate>
    </item>
    <item>
      <title>One template to rule them all</title>
      <link>https://write.moxnet.eu/one-template-to-rule-them-all</link>
      <description>&lt;![CDATA[#leadership #emacs&#xA;&#xA;As a manager one of my tasks is to do yearly performance evaluations of the employees in my team.  &#xA;I take this very seriously, as although I speak regularly with my people about tasks and behaviors, this yearly review gives me time to pause and reflect deeper about the stuff I (and the company) find important and how does the employee measure against that.  &#xA;During the year I keep notes of all 1:1 meetings we have and also of stuff that happens between them that catch my eye, positive as well as possible improvement points. During the yearly review preparations, I sit down and go thru all the notes in order to consolidate the feedback I want to give to the employee.  &#xA;&#xA;!--more--&#xA;&#xA;In the company I work, we have multiple systems where I need to fill out parts of the performance review:  &#xA;&#xA;There is a system where I need to document some high level work and behavior goals for the year. I can also do some basic commenting there, but the system feels like it&#39;s from 1985 😀.&#xA;Then we have a system where employees can document their concrete contributions during the year. This really feels modern and limited in functionality 🤣.&#xA;Additionally to that there are 2 different systems where we manage their monthly salary and performance bonuses. Don&#39;t ask me why 🤨.&#xA;Then we have some special new contracts where everything is kind of free flying, as the software systems are not yet up and running 😁.&#xA;&#xA;In order to be able to structure my thoughts as well as the feedback, I decided to create a custom template. This way I have one document that I can use to structure my preparation, guide the employee thru the feedback meeting and share with him/her afterwards. The document also includes the links to all the system above and provides more context to the information documented there.  &#xA;&#xA;Where did I create it? In #emacs #orgmode of course 😁. You can find the source here ... and &amp;#x2026; yes, I work in a German company.  &#xA;&#xA;Use it, adapt it and make your employees happy!  &#xA;&#xA;br&#xD;&#xA;- -&#xD;&#xA;&#xD;&#xA;Have any thoughts or comments?]]&gt;</description>
      <content:encoded><![CDATA[<p><a href="https://write.moxnet.eu/tag:leadership" class="hashtag"><span>#</span><span class="p-category">leadership</span></a> <a href="https://write.moxnet.eu/tag:emacs" class="hashtag"><span>#</span><span class="p-category">emacs</span></a></p>

<p>As a manager one of my tasks is to do yearly performance evaluations of the employees in my team.<br>
I take this very seriously, as although I speak regularly with my people about tasks and behaviors, this yearly review gives me time to pause and reflect deeper about the stuff I (and the company) find important and how does the employee measure against that.<br>
During the year I keep notes of all 1:1 meetings we have and also of stuff that happens between them that catch my eye, positive as well as possible improvement points. During the yearly review preparations, I sit down and go thru all the notes in order to consolidate the feedback I want to give to the employee.</p>



<p>In the company I work, we have multiple systems where I need to fill out parts of the performance review:</p>
<ul><li>There is a system where I need to document some high level work and behavior goals for the year. I can also do some basic commenting there, but the system feels like it&#39;s from 1985 😀.</li>
<li>Then we have a system where employees can document their concrete contributions during the year. This really feels modern and limited in functionality 🤣.</li>
<li>Additionally to that there are 2 different systems where we manage their monthly salary and performance bonuses. Don&#39;t ask me why 🤨.</li>
<li>Then we have some special new contracts where everything is kind of free flying, as the software systems are not yet up and running 😁.</li></ul>

<p>In order to be able to structure my thoughts as well as the feedback, I decided to create a custom template. This way I have <strong>one document</strong> that I can use to structure my preparation, guide the employee thru the feedback meeting and share with him/her afterwards. The document also includes the links to all the system above and provides more context to the information documented there.</p>

<p>Where did I create it? In <a href="https://write.moxnet.eu/tag:emacs" class="hashtag"><span>#</span><span class="p-category">emacs</span></a> <a href="https://write.moxnet.eu/tag:orgmode" class="hashtag"><span>#</span><span class="p-category">orgmode</span></a> of course 😁. You can find the source <a href="https://moxnet.eu/s/94SLreK3jbce6Xz">here</a> ... and … yes, I work in a German company.</p>

<p>Use it, adapt it and make your employees happy!</p>

<p><br></p>

<hr>

<p><em>Have any <a href="mailto:kemal@moxnet.eu">thoughts or comments</a>?</em></p>
]]></content:encoded>
      <guid>https://write.moxnet.eu/one-template-to-rule-them-all</guid>
      <pubDate>Tue, 25 Feb 2025 17:19:30 +0100</pubDate>
    </item>
  </channel>
</rss>