Is AI Writing the Articles on This Blog?

While sipping my coffee and reading my old articles, I noticed something. We've spent so many years dealing with tech, code, and foreign docs that the structure of our sentences got ruined. It's like we ended up with a weird dialect of Turkish that only we developers understand, sounding like robots from sci-fi movies. This is exactly where I use my beloved AI (LLMs) as an editor—to fix my broken Turkish and build fluent sentences that won't bore you to death. But let's start by answering the big elephant in the room:

Is AI writing the articles on this blog?

No.

Not a single piece of human-written text on this blog was generated by AI, and I have absolutely no intention of changing that. All those weird grammatical errors, false assumptions, typos, and annoying phrasing belong entirely to me.

---

🤝 The "Social Contract" with the Reader#

I don't use large language models directly to write articles. Neither on this blog nor in my professional work.

That's because making people read raw AI-generated text feels like a breach of that invisible social contract¹ between us. When I publish a piece under my name, I want you to know that I actually understand the topic and stand by my words. Showing respect to your time and effort is the only way to do it.

Pumping pages of filler text using AI just to inflate the word count and dumping it in front of readers is like inviting a friend over for coffee and playing them a tape recording of yourself instead of talking.

If I'm going to make AI write about a topic and send it to you, and you're going to use another AI to summarize it, what are we even doing here? Instead of that, I would rather give you the direct cues to research the topic yourself with your own AI. That saves you a lot of time.

Personally, I value function over form in professional life too. If you have a half-page idea, just give me that half-page, my friend. Don't fluff it up with Claude or ChatGPT to serve me a five-page report. If I want to know what AI thinks, I'll go and ask it myself. Besides, I'd get a much more personalized answer tuned to my own context that way!

---

💻 Why Writing Code and Writing Articles Are Different#

I draw a hard line with AI when it comes to writing articles, but things change when coding. Of course, I don't blindly hand over my projects' or this blog's code to AI to fill it with temporary patches written via "vibe-coding" that I don't even understand. I design the architecture, logic, and every line of code myself. AI here acts merely as a smart assistant speeding things up. (If you want to set up your own coding assistant and work with local models, you can check out my guide on Local AI Setup Guide (LM Studio & VS Code).)

So, why are writing code and writing articles different? The core goal of code is to give instructions to a computer; once the logic is solid and works, the process runs. But the purpose of writing is to connect with another human being and share ideas. Having AI write raw text ruins the sincerity between us, whereas using a coding assistant is just a technical tool making our lives easier.

---

🚫 Link Translators and Ad Hunters#

I use AI in writing strictly as an editor and critic. It is a fantastic helper for cleaning up broken sentences and fixing typos. But I have never seen AI as a tool to just "generate content." (You can also check out my post on AI Detector Nonsense where I discuss the inconsistency of these detection tools.)

I never ask AI to write about topics I don't care about or find interesting. I have no interest in grabbing every technical link on the web, running it through AI for a quick translation, and stuffing it with ads for easy money. Every word on this blog carries the mark of genuine curiosity, sleepless nights, and tinkering with systems.

We love AI and place it at the center of our lives as an assistant that makes things easier; but to preserve that sincere and human bond with the reader, we will always keep the pen in our own hands.