Reader

Brainiac v1.1 released

#emacs #orgmode #brainiac #gtd #productivity

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.

If you're new to Brainiac, check out the original introduction to learn about the philosophy behind this configuration.

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.

✅ What’s New in v1.1

• Default search now uses rgrep instead of find-grep-dired
• Added ultra-scroll for smoother scrolling over large images
• Removed DONE tasks from agenda to reduce clutter

• New focused Day Agenda:

  • Scheduled tasks, deadlines, and priority backlog ([#A])

• New Week Agenda:

  • Full week view + entire backlog to support weekly review flow

• Statistic cookies auto-update on save (accurate project status always)

• Improved print CSS to prevent long lines from overflowing

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

Get your update from here.

📬 Feedback & Ideas

Have feature suggestions or questions? Share your thoughts — and follow for future Brainiac updates.

#reflection

Everywhere we look, be it blogs, articles, TV, printed media, books ... everyone is talking about increasing productivity, self-improvement, the best health plan we have to try, next gadget that will make our life easier ...

Isn't all of this there just to further fuel the modern capitalist consumerist machine?

Are we setting the wrong goals and priorities in life?

After my family suffered a great personal loss last year, I started asking myself some important but very uncomfortable questions:

• You are in the second half of your forties, how much time is left?
• Are you happy with your life?
• What did you achieve until now, is it enough?
• What is the meaning of it all?

I didn't find answers to all of these questions, but I think I found a most important goal of them all.

Prime Directive: I want to live at least 90 years and enjoy this time with the people I love.

Put against the other goals I had until now:

• How do I earn more money, to be able to afford a vacation in Japan?
• Get a grip on the new technologies, that could make you obsolete.
• Speed up, organize yourself better, improve presenting skills, ...

it makes them look pale and unimportant.

I have a feeling that most of my “old” goals were dictated externally, by a society that is itself driven by the agenda of capitalism (constant growth and increasing consumption) and doesn't have the benefit of the individual in mind. Even though some of the thinkers, influencers, bloggers ... think that they are actually doing and preaching something “completely different than the evil capitalists”.

I am currently in the process of rethinking all my goals and actions, that do not align with the prime directive from above. Let's see where this brings me ...

#leadership #reflection

This is it. Final post of the series, as I think the transition is now over. In this post I will try to recapitulate what I achieved, learned and messed up in the last 48 months.

Achievements

Of course one of the perspectives on being a successful team lead are the things you contributed to the company:

• I have hired 15 people to work for me directly and on-boarded 4 offshore engineering teams (6-8 people SCRUM teams) in order to be able to reach the project goals.
• Under my supervision the teams have defined testing processes and methods that successfully passed the ASPICE assessment.
• We also build a testing infrastructure including some 50 HiL benches, integrated some off-the-shelf testing solutions and developed additional tools, pipelines etc., needed to “run the show”.
• Last but not least, we delivered the results needed from us and helped the project reach it's first carline SOP.

The fairy tale of managers not needing technical experience

There is this misconception that in order to be a manager, you just need to be able to create some sort of a plan for your team and then push them to reach that plan. In order to do this, you have to set up KPI's and track them daily. You do not need to understand what they are doing in detail, as your KPI's will give you insight if something is going wrong and then you correct it. You should empower your team to do their technical work and make decisions, which will keep them motivated and performing.

In my experience it doesn't work like that. If you are working in R&D and are leading technical teams, you need to understand at least 70-80% of the technical work and ideally you have done that, or similar work, yourself before. This is why:

• Your employees will need on-boarding, guidance, understanding, help ... with their technical tasks. It's not possible to delegate all of these things to other technically more skilled people in your team. Of course you should get seniors to onboard and mentor your juniors, but if you exaggerate, then your seniors will at some point complain that they can not do their own tasks.

• Your employees will need help in setting priorities and making decisions. This is almost impossible, if you do not have enough technical experience to do this properly. Let's take for example that your team is responsible for testing some software:

  • If everything is 100% passed (which I would highly question 😆) , decision making is trivial.
  • If a test report shows 80% – 20% rate, they will probably come to you to make a decision. How will you do this, if you do not have either the experience to make the judgment yourself or know someone, who can help making the judgment?

Manage expectations

Before I started this job, one of my mentors told me to get prepared to be a complain box. This is a sentence I repeated a lot of times in my head in these 4 years and to other people, when they asked me about my key learning's.

Basically a lot of people (your employees, your boss, your colleagues, employees from other teams, people from the company you didn't know existed ...) will try to dump their complaints, problems, requests, tasks etc., on you. They'll call you up, invite you to meetings, come to your desk, send you E-Mails, message you ... put your communication channel here ..., and try to somehow engage you in stuff that's bothering them, that needs solving or demands your support.

This simple strategy should help you not overload yourself and actually focus on delivering what you are responsible for:

• Who is the person contacting you? If not on your priority list, ignore them in a friendly way 😝.
• Listen or read carefully, but do not respond directly no matter how many URGENT, ASAP, CRITICAL keywords are contained in the communication.
• Take a minute to think about the content and ask yourself “I am the first responsible for solving this?“.
  • If your answer is a definite YES, then add it to your TODO list.
  • If your answer is a NO or UNSURE, just don't do anything and wait it out. If it really is your responsibility, it will come back again either with more details or more push by people payed better then yourself.

You can not solve all the problems that your team members, projects or company have. This is what the over-excited and over-motivated me from 4 years ago had to painfully accept, when I moved into stress levels that could have led to a burnout. You have only 24 hours in a day and 8 of those you should sleep. The rest needs to be divided between work tasks, private obligations, quality time with your loved ones and time for yourself. If you do not take time for yourself, you will burn out.

Accept errors

During my tenure so far not everything that I wanted to do or implement in the team worked. Sometimes I did something and it worked, e.g. team accepted it and it started bringing positive impacts. But a lot of times I also had to give up on something that looked good to me, but the people just didn't want to accept it. Of course you could try to push it thru with all the might, as you sometimes really have to do, but you should really be careful what battles you want to fight this way. At the end, you should not become a dictator ...

Accepting that something didn't work and openly saying “Hey, I wanted us to try this but it didn't work because ...” has two positive effects:

• You show the team that their opinions matter, dictators never last long.
• You show that you are human and make errors, which signals your people that it's OK to try something and fail, which is a path to continuous improvement and innovations.

Also important ...

There is a ton of other stuff that is important and you probably read it somewhere else as well, so I'll just list it and not go into details:

• Build yourself some sort of productivity system like GTD or Second Brain. I used the Brainiac. You will have more tasks, projects, notes, E-Mails, messages ... than you can process in your head. Make sure they do not get lost and you can surface them when needed.

• Treat peoples private life with respect and understanding. Any sort of stress or problems in personal area will directly influence the employees performance. Give them space and time to deal with it and signal that you are fine if they temporary cut down on their tasks in order to sort out their personal life. They will (mostly) come back stronger and more motivated to push things forward.

• Panic and stress are infectious. Of course your employees will see that you are under stress, as we are all humans. But try to control yourself and openly communicate, e.g. like this “It's hard currently, too many things going around. My TODO list is bursting. I need some time to go thru all of this, maybe I will not be as reachable as usual but bear with me, we'll get it done.”, to keep the panic from spreading.

• Keep a keen eye on the small changes in peoples behavior and communication, they will give you valuable pointers on what is happening in your teams. People will mostly not talk openly in a team meeting, if something dodgy is happening on the personal level in the team. But there will be some side looks, strange comments etc., that will give you valuable pointers for your next 1:1 sessions.

What lays ahead?

There is a lot of tasks, projects, problems, errors ... laying in front of me in the future. But I am not over-excited, over-motivated, scared, overwhelmed, inexperienced ... anymore.

During my tenure as a team lead, as well as in my previous roles as project lead and developer, I gathered experience and confidence needed to tackle those things.

Will I get it all done correctly? Definitely no, but this is also part of the journey and a possibility to learn something new.

#emacs #brainiac #emacscarnival202506

I am glad to announce that my custom Emacs configuration Brainiac has reached release status. I am now using it without major changes since a couple of weeks, so it's time to freeze this version if other people want to use it.

Introduction

Why do I aim to have a minimal configuration? I am a perfectionist and tend to get lost in details. When a configuration gets larger, I loose time by tweaking it over and over again. By keeping the configuration minimal, I reduce the danger of going down the Emacs rabbit hole and increase the probability that I will focus on more important things in life.

Brainac is aimed to be a simple and easy to understand configuration for task management and note taking. It's not aimed at programmers, but at people trying to implement a workflow like GTD or build something like a Second Brain without overcomplicating the process, e.g. connection graphs, AI support etc.

The configuration is very opinionated, as it's based on my workflow. I am not trying to make it generic, just clean and easily extendable. I stick with the built-in packages in order to reduce dependencies and complexity.

Short description

Noteworthy stuff: – I picked up some sane defaults from multiple sources, like turning on the revert mode, enabling smart parenthesis, tuning of built-in completion engine etc. – The tasks and notes should look nice and readable, because of this I use the modus-operandi theme and style some things additionally to either push them to the background or to make them stick out more visually. – You can easily capture tasks, webpage links/quotes (using org-protocol) and screenshots (using org-download, org-attach and flameshot). – A simple journal with timestamped entries is configured in the capture templates. – Notes are also captured over a template and you can assign categories to them. Format is inspired by Denote. – You can export the notes to HTML (uses custom CSS) or Markdown. From there you can print to PDF or other formats. – Additionally to normal org-clock functionality, you can define a special task and clock in it per default with C-c j w. I use this to clock my work time.

I will not go deeper into details of the configuration, go thru it and explore. Most of the stuff can be understood by reading the help on variables and functions.

Currently I am using the configuration with Ubuntu Linux LTS 24.04 KDE and Emacs 29.3. If you use something else, you will probably have to tweak it.

Structure and install

The configuration consists of two major files: – brainiac.org which contains the configurations that will be tangled to early-init.el and init.el, – brainiac.css a simple CSS for the exported notes.

Unpack the zip file from here to your HOME folder ~/brainiac. You will get the structure like this:

~/brainiac/
    -- config/ <- this is where the configuration files are
    -- notes/ <- this is where all notes go
    -- attach/ <- this is where the attachments land
    -- export/ <- this is where the exported files are
    -- main.org <- this is the main org file to use for tasks, projects etc.

After unpacking open the brainiac.org and tangle it.

External apps needed are: – Org Capture for Firefox – Flameshot

Workflow

I provide a template for main.org that is based on the workflow I use:

• Top level headings are categories in my life.
• Under top level headings I create tasks and put them thru the states TODO, PROG, WAIT, DONE or CANC to track their progress.
• I use tags to provide more context to tasks, e.g. work, names, project relation etc.
• If a task comes from an Email I deal with this by using the following form TODO @ "Subject_of_the_Email", then it's easy to find it in my Emails when I need extra information on the task.
• Your daily agenda is at C-c a n. That will show you scheduled tasks for today and deadlines coming up, I work on that first.
• Every task that is not scheduled or has no deadline, is shown in a backlog below the day tasks. I use priorities to sort this backlog and give me clarity on what to work next.
• Use PRJ tag to mark your projects that will be broken down to tasks. I usually use statistic cookies at the end of the name of the project to show me an overview of tasks in the project.
• You can have a look at your projects with C-c a P. I inspect the projects once a week during the review, to see if some of them need attention, e.g. they are stuck C-c a #.
• When showing notes to other people I usually do a quick C-c C-e h o which exports the note to HTML and shows it in Firefox.

Open for feedback and improvements

If you have feedback, improvement propositions etc., just reach out to me.

#emacscarnival202506 #brainiac

Somewhere during the COVID pandemic I started checking out #emacs, because of a talk I saw on #orgmode that tickled my curiosity.

In the beginning I didn'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.

Over the years as my proficiency grew, so did my Emacs config. Although I regularly removed packages I didn'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't really reach the state of bankcruptcy, but I gathered some #elisp snippets I didn't understand or simply didn't remember why I got them at all.

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.

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.

You can follow how the configuration progresses here: Brainiac. 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.