Skip to content

Both.org

News, Opinion, Tutorials, and Community for Linux Users and SysAdmins

Primary Menu
  • About Us
  • Computers 101
    • Hardware 101
    • Operating Systems 101
  • End of 10 Events
    • Wake Forest, NC, — 2025-09-20
  • Linux
    • Why I use Linux
    • The real reason we use Linux
  • My Linux Books
    • systemd for Linux SysAdmins
    • Using and Administering Linux – Zero to SysAdmin: 2nd Edition
    • The Linux Philosophy for SysAdmins
    • Linux for Small Business Owners
    • Errata
      • Errata for The Linux Philosophy for SysAdmins
      • Errata for Using and Administering Linux — 1st Edition
      • Errata for Using and Administering Linux — 2nd Edition
  • Open Source Resources
    • What is Open Source?
    • What is Linux?
    • What is Open Source Software?
    • The Open Source Way
  • Write for us
    • Submission and Style guide
    • Advertising statement
  • Downloads
  • Home
  • Team of one? The Zen postmortem
  • System Administration

Team of one? The Zen postmortem

The practice of yoga offers sysadmins valuable lessons in self-examination.
David Both March 10, 2024 4 minutes read
zen_rocks_stack_blue_yoga_peace

Image by: Pixabay by mouse-driver, CC0

The practice of yoga offers sysadmins valuable lessons in self-examination.

Jen Wike Huger, a friend of mine and formerly an editor on the Opensource.com staff, wrote a 2018 article Living on the command line: Why mistakes are a good thing about how to fail gracefully and why it’s necessary to do so. In addition to discussing the fact that mistakes are inevitable, Wike Huger also discussed responses to those mistakes and the use of postmortems as a means of blamelessly moving forward. She lists five steps for making these meetings successful.

But how do you conduct a postmortem when you are the entire team? This can be a challenge, but I find that my yoga classes have given me a solution. The following excerpt from my book, The Linux Philosophy for SysAdmins, describes my process:


As a student of yoga, the first thing I do when starting my (almost) daily practice, whether in my own little yoga room or in a class, is to find my center. This is time to just be, and to use my mind to explore the physical aspects of my being while opening up to the experience of just existing.

Having done it myself, I suggest that this is an excellent method for exploring our thinking and reasoning as sysadmins. That is not to say I use this technique to solve problems, but rather to explore my own methods for problem-solving.

Many times, after solving a problem, particularly a new or especially difficult one, I spend some time just thinking about the problem. I start with the symptoms, my thinking process, and where those symptoms led me. I take time to consider what finally led me to the solution, things I might have done better, and to identify what new things I might want to learn.

It gives me an opportunity to, as an individual, perform what we used to call a “lessons learned” meeting at one of my former places of employment. That was an opportunity to look at what we as a team did right and what we could have done better. The best and yet hardest part now is that I don’t have others to help me understand what I could have done better. That makes it all the more important for me to do this as much as possible.

It is not necessary to practice yoga in order to do this. Just set aside some time, find an empty space where you won’t be interrupted, close your eyes, and contemplate. Breathe, relax, and calm your mind before trying to review the incident. Start from the beginning and think your way through the incident. Review the complete sequence of events and the steps you used to ultimately find the solution. The things you need to know and learn will make themselves clear to you. I find that this form of self-evaluation can be quite powerful.

I also like to take a moment before I start to work on a new problem to center myself. This opens my mind to the possibilities. First, there are the possibilities that represent the likely causes of the problem. Then there are the possibilities that represent the methods and tools I have to locate the causes of the problem. Finally, there are the possibilities that represent the ways that there are to fix the problem.


You may find other methods for performing this essential self-evaluation. I know some people who write up a report about the incident. I sometimes do this too, to focus my own thoughts and to provide the customer with a report that can explain what happened, especially when things were not going well. With something like this, self-awareness, truth, and openness to your own errors and mistakes are important—especially because there is no one else to point these out.

Self-examination is not easy, but my yoga experience has enabled me to do it with much less angst and a more truthful approach.

Tags: Post Mortem Zen

Post navigation

Previous: Configure a Linux workspace remotely from the command line
Next: Convert your Windows install into a VM on Linux

Related Stories

th-2358250818
  • Kernel
  • Linux
  • Linux 101
  • System Administration

Why I Really Like Linux

David Both March 12, 2026
Liquid-Cooling-001
  • Fedora
  • Installation
  • Linux
  • System Administration

Why I Installed Fedora Server on My Primary Workstation — and How

David Both January 26, 2026
rh_003499_01_other21x_cc
  • Maintenance
  • Networking
  • System Administration

Network Upgrades Completed — Sort of

David Both January 24, 2026

Random Quote

Any given program will expand to fill all available memory.

— Laws of Computer Programming

Why I’ve Never Used Windows

On February 12 I gave a presentation at the Triangle Linux Users Group (TriLUG) about why I use Linux and why I’ve never used Windows.

Here’s the link to the video: https://www.youtube.com/live/uCK_haOXPFM 

David Both ATO Interview

Last October at All Things Open (ATO) I was interviewed by Jason Hibbits of We Love Open Source. It’s posted in the article “Why today’s AI isn’t intelligent (yet)“.

Technically We Write — Our Partner Site

Our partner site, Technically We Write, has published a number of articles from several contributors to Both.org. Check them out.

Technically We Write is a community of technical writers, technical editors, copyeditors, web content writers, and all other roles in technical communication.

Subscribe to Both.org

To comment on articles, you must have an account.

Send your desired user ID, first and last name, and an email address for login (this must be the same email address used to register) to subscribe@both.org with “Subscribe” as the subject line.

You’ll receive a confirmation of your subscription with your initial password as soon as we are able to process it.

Administration

  • Log in
  • Entries feed
  • Comments feed
  • WordPress.org

License and AI Statements

Both.org aims to publish everything under a Creative Commons Attribution ShareAlike license. Some items may be published under a different license. You are responsible to verify permissions before reusing content from this website.

The opinions expressed are those of the individual authors, not Both.org.

You may not use this content to train AI.

 

Advertising Statement

Both.org does not sell advertising on this website.


Advertising may keep most websites running—but at Both.org, we’re committed to keeping our corner of the web ad-free. Both.org does not sell advertising on the website. Nor do we offer sponsored articles at this time. We’ll update this page if our position on sponsorships changes.

We want to be open about how the website is funded. Both.org is supported entirely by David Both and a few other dedicated individuals.

 

 

Copyright © All rights reserved. | MoreNews by AF themes.