Why I Started This Blog

I spend a large part of my day in front of a computer. Sometimes I am researching a vulnerability, sometimes I am fighting a Linux error whose cause makes no sense, and sometimes I spend three hours staring at a terminal over a task I thought would take two minutes.

The usual.

When I solve a problem, I normally tell myself, “That is done; I know this now.” Two weeks pass, the same problem appears again, and this time I ask myself:

How did I solve this last time?

I remember the command but not why I used it. I found the solution, but lost the reasoning somewhere along the way. Then it is back to researching, testing, and struggling with the same problem.

I started this blog partly to stop repeating that cycle.

What will I publish here?

This will not be a place reserved for long, overly serious technical articles.

Sometimes I will share something I learned during security research. Sometimes I will document the fix for a ridiculous Linux error. Sometimes I will write down the problems that took hours to investigate and eventually came down to a single command.

In general, I plan to cover:

• Web security
• Networking fundamentals
• Linux
• Penetration testing notes
• Responsible disclosure processes
• Tools I build
• Lessons from CTF competitions
• Mistakes I make
• Topics that make me ask, “Why did I not learn this sooner?”

Some articles may be long. Others may consist of only a few paragraphs. If something can be explained briefly, there is no reason to turn it into an epic just to make it look substantial.

I am not writing because I know everything

The reason for this blog is not to say, “I know everything; now I will teach you.”

In cybersecurity, you should probably be cautious around anyone who says that.

This field changes constantly. Something you know to be correct today can become outdated within months. A new technology arrives, a new vulnerability is discovered, a tool changes, and systems evolve.

I will document what I encounter while learning. If I get something wrong, I will correct it. If information becomes outdated, I will update it.

In short, this is not the story of completed expertise. It is a record of an ongoing learning process.

Where do I draw the line in security research?

I will publish security research, but I will not include details that could harm live systems, expose sensitive data, or put people at risk.

Explaining how a vulnerability was discovered is not the same as leaving working exploit code for everyone to use.

My goal is not merely to find vulnerabilities. It is to understand the problem correctly, explain its impact, and, where possible, contribute to fixing it.

That is also where security research becomes interesting.

Sometimes everyone else sees a website behaving normally while you notice one small detail that does not fit. You investigate it, research it, and discover that the tiny anomaly points to a much larger problem.

I admit that I enjoy this part.

Why a public blog?

I could keep these notes on my computer. In fact, I already have years of notes scattered across directories, text files, and filenames that even I no longer understand.

Notes that remain on a computer often have little value. You write them and never open them again.

Publishing here forces me to write more carefully. The thought that someone else will read a piece also makes it obvious whether I genuinely understand the subject.

If I cannot explain a topic clearly, I probably do not understand it completely either.

And if a problem that cost me hours can help another person solve it in five minutes, that is a good outcome.

The first entry

This is the first article on the blog.

From here on, I will share topics I genuinely find useful, ranging from small terminal crises to lessons from security research.

Some posts will be serious, some technical, and some will be in the “why did this error cost me three hours?” category.

In short, I started this blog to retain what I learn, document the technical absurdities I encounter, and share notes that might help somebody else.

Let us see where it goes.