Shifting My Priorities Toward System Administration

Over time, I have been thinking more seriously about where I want to take my career and what kind of work I want to prioritize. While I still enjoy software development and continue to have a strong interest in building software, libraries, testing tools, and infrastructure through Fossil Logic, I have started shifting my primary focus toward becoming a system administrator.

This is not necessarily a departure from software development. If anything, I think the two areas complement each other extremely well. System administration requires understanding operating systems, networking, hardware, security, automation, troubleshooting, deployment, monitoring, and the many practical details that keep computers and services functioning. Software development provides another set of tools for solving those problems.

That combination is particularly appealing to me.

I have always enjoyed working with systems and figuring out why something is not behaving the way it should. Whether the problem is a build failure, a dependency issue, a configuration problem, a networking problem, or some other unexpected behavior, there is something satisfying about working through the problem systematically until I understand what is actually happening.

That mindset seems naturally suited to system administration.

My goal is to develop myself into someone who can responsibly manage computer systems rather than simply write applications that run on top of them. I want to understand the machines, operating systems, services, networks, storage, security practices, automation, and infrastructure that software depends upon.

At the same time, I do not intend to abandon Fossil Logic.

If anything, I think Fossil Logic could become an excellent side project alongside a career in system administration. It gives me an opportunity to continue developing software without making software development my sole professional focus. I can continue maintaining the Fossil SDK, Fossil Test, Fossil IO, and the other projects while applying the practical knowledge I gain from working with real systems.

There is also a useful relationship between the two.

A system administrator who understands programming has an advantage when repetitive tasks need to be automated, when internal tools need to be created, or when existing software needs to be diagnosed. Likewise, a programmer who understands system administration has a better appreciation for how software actually operates in production environments.

I would like to build that combination of skills.

Fossil Logic can also remain a place where I experiment. I can continue developing tools, improving testing infrastructure, exploring database technology through Blue Crab, and working on other ideas without necessarily expecting every project to become a commercial product. That makes the project much more enjoyable to me.

There is something appealing about having a stable professional career in system administration while maintaining an independent software project on the side. It provides structure without requiring me to give up the creative and technical work that I enjoy.

I also think becoming a system administrator would give me a broader technical foundation. Software development can sometimes become very specialized. System administration naturally exposes a person to many different layers of computing. One day might involve troubleshooting a service, another might involve networking, another storage, another security, and another automation.

That variety is attractive to me.

I want to become the kind of technical professional who can look at an entire environment and understand how the pieces fit together. Knowing how to write code is useful, but knowing how that code interacts with the operating system, filesystem, network, hardware, services, permissions, and other infrastructure is equally important.

This shift in priorities therefore feels less like abandoning one path and more like broadening my capabilities.

Fossil Logic remains important to me because it represents my interest in building things. System administration represents my interest in keeping things working. I think there is considerable value in being able to do both.

For the foreseeable future, I want to put more effort into developing the skills necessary to become a competent system administrator while continuing Fossil Logic as a serious side project. I am not looking to turn every hobby into a business or force Fossil Logic into something it does not need to be.

Sometimes a project is valuable simply because it gives you a place to learn.

That is what Fossil Logic can continue to be for me.

My professional priority can be system administration, while Fossil Logic remains the place where I continue writing software, experimenting with ideas, improving my engineering skills, and building tools that I find useful.

I think that is a practical balance.

Rather than trying to make software development carry the entire weight of my career, I can pursue system administration as my primary profession and keep software engineering as an important part of my technical life. In many ways, the combination may ultimately make me better at both.

The goal is not to choose between being a programmer and being a system administrator. The goal is to become someone who understands computers from more than one perspective.

That is the direction I want to pursue now: system administration as my primary career, with Fossil Logic continuing as a serious and productive side project.

I think it is a good fit for where my interests have been heading, and I am looking forward to seeing what I can build—and what I can keep running—along the way.