Hello World

Every project needs a first output.

For some, it is a blinking LED.
For others, it is a clean terminal prompt, a successful build, a green CI pipeline, or a small web page that finally renders without errors.

For this website, it is this post.

Hello World.

This is the first note on osmandagdeviren.com.tr, and I want it to stay simple. No exaggerated promises, no perfectly polished introduction, no attempt to make this place look bigger than it is on day one. This website starts as a personal space: a place where I can write, document, test ideas, keep technical notes, and leave useful traces for my future self.

If those traces help someone else along the way, even better.

Why this website exists#

I have always liked the idea of owning a small corner of the internet.

Not just a profile page on someone else’s platform. Not just scattered notes across chats, repositories, bookmarks, and forgotten text files. I wanted a place that feels closer to a technical notebook: something I can shape, break, fix, redesign, and extend over time.

This website is not meant to be a perfect knowledge base from the beginning. It is more like a living archive.

Some posts may be structured guides.
Some may be debugging notes.
Some may be quick reminders.
Some may be opinionated experiments.
Some may simply document what worked, what failed, and what I learned while trying to make something work.

That is the point.

Real technical work is rarely as clean as final documentation makes it look. Systems fail. Commands behave differently than expected. Drivers break. Containers refuse to start. Models do not fit into memory. A configuration line that looks harmless can waste hours. Sometimes the final answer is elegant; sometimes it is just a tiny fix hidden inside a long trail of errors.

I want this site to preserve that trail.

What I will write about#

The topics here will probably move around the things I already spend time with: Linux, self-hosting, homelabs, Docker, Proxmox, automation, web development, artificial intelligence models, performance tests, hardware experiments, and all the small technical details that become important only after something breaks.

There will be posts about tools I use.
There will be posts about systems I build.
There will be posts about mistakes I make.
There will be posts that are mostly notes to myself.

I do not want every article to sound like a tutorial written from a distance. I prefer writing closer to the real process: what I tried, what happened, what confused me, how I investigated it, and what finally solved the problem.

That kind of writing may not always be the shortest path to an answer, but it is often the most useful path when you are dealing with the same problem in the real world.

A personal technical archive#

One of the main reasons for starting this blog is simple: I forget things.

Not the big ideas, but the exact commands. The small flags. The order of operations. The workaround that fixed a weird issue at 03:00. The reason I chose one tool instead of another. The context behind a configuration file that looked obvious when I wrote it.

Writing things down turns temporary solutions into reusable knowledge.

So this website is also an attempt to build my own memory layer. A searchable, public, versioned place for the things I learn while working with software, hardware, infrastructure, and automation.

Maybe some posts will age badly. Maybe some solutions will become obsolete. That is fine. Technology changes, and a good archive should show that change instead of pretending everything is timeless.

Shared knowledge#

I believe knowledge becomes more valuable when it is shared.

The notes, guides, experiments, and explanations published on this blog are not meant to stay locked inside a private archive. They are here to be read, used, adapted, discussed, improved, and carried forward by others, as long as the original work is respected.

That is why the blog posts on this website are published under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License unless stated otherwise.

In simple terms: you can share and adapt the content, but you should give proper credit, avoid commercial use, and keep derivative works under the same license.

This feels aligned with the kind of internet I want to contribute to: an internet where useful knowledge does not disappear inside closed platforms, private notes, or forgotten chat logs, but keeps growing through people who learn from each other.

If something I write here saves someone a few hours, helps them understand a problem, or gives them a starting point for their own work, then this blog has already done something useful.

The tone of this place#

I do not want this blog to feel overly corporate or artificially polished.

I want it to feel practical, personal, and honest.

When something works, I will write what worked.
When something does not work, I will try to explain why.
When I am unsure, I will say that I am unsure.
When a post is just a note, it will remain a note.

The goal is not to look like I have everything figured out. The goal is to keep learning in public and to build a useful technical archive over time.

First commit#

A “Hello World” is usually not impressive by itself.

It does not solve a major problem. It does not prove that the architecture is good. It does not guarantee that the project will become useful. It simply proves that the first connection has been made.

The system runs.
The page exists.
The first output is visible.

That is enough for a beginning.

So this post can stay here as the first commit of this website’s written archive.

Hello World.