About geekBlog

$ whoami
Christian – Linux sysadmin, developer, and chronically curious.

I'm Christian. At work and in my spare time, I deal with Linux, servers, networks, email infrastructure, automation, and software development.

geekBlog is my personal place for technical topics, my own projects, and anything I find interesting enough to understand properly and write down.

What this is about

The focus is on topics like:

• Linux and system administration
• Server services, networking, and security
• Email, DNS, and deliverability
• Python, Django, and automation
• APIs and self-built tools
• Artificial intelligence and local AI applications
• Open-source software and technical experiments

Now and then, it goes beyond classic IT topics. Then there are articles about science, pop culture, survival, or other questions worth a closer look.

Why I write

Many technical problems seem more complicated at first than they really are. Often all that's missing is a clear explanation, a working example, or the key connection between several separate pieces of information.

That's exactly where my articles come in.

I try to present topics so that you can not only reproduce them but also understand them. That includes concrete commands and code examples as well as background, possible sources of error, and the reasons behind certain decisions.

I don't write from the perspective of an all-knowing textbook. Many posts grow out of real problems, my own projects, or the wish not to have to piece a solution together again next time.

What I aim for

The content on geekBlog should:

• be technically easy to follow,
• do without needless marketing talk,
• contain working and, where possible, complete examples,
• name limits, downsides, and trade-offs,
• give beginners a way in without boring experienced readers.

When technology changes, older solutions can become outdated. That's why I try to keep articles up to date and work in changes transparently.

Not a perfect lab

Not every project starts with a complete architecture and a flawless plan. Sometimes all there is at the start is an idea, an error in the log, or the question:

"Why doesn't this work the way I expected?"

Questions like that often lead to the most interesting solutions, and now and then to the best articles too.

$ cat motivation.txt
Understand things.
Solve problems.
Capture knowledge.
Share experience.

Hints, corrections, and constructive additions are welcome. You'll find contact details in the legal notice.