Why I Started This Blog

I created this blog to document what I build, what I break, and what I learn along the way.

I’ve spent time exploring different areas of tech, from development to cybersecurity, and slowly moved toward systems, networking, and infrastructure.

At some point, I realized that what I enjoy most isn’t just using tools or following tutorials. It’s trying to understand what’s actually happening behind the scenes.

Why something behaves the way it does. Why something breaks. And sometimes, why it works when it probably shouldn’t.

Most of the time, I’m just working on small projects, testing setups, or messing around in my lab. Nothing fancy. Just trying things, seeing what happens, and going from there.

Some of it works. A lot of it doesn’t.

But the interesting part is always in between, when something doesn’t behave like expected, and you start digging into it.

There’s no real routine. It usually ends the same way: late nights, a terminal open, trying to figure something out. Fixing one thing, breaking another, and going a bit deeper each time.

Some posts will be clean and structured. Others will just be notes written after those sessions, while things are still fresh.

I don’t really have a strict plan for this blog. It’s more a way to keep track of progress, ideas, and mistakes over time.

If something here helps someone, even a little, then it’s already worth it.