Being a Writer in the Era of Writer/AI Slop

After seven years of writing technical articles, during this time I have loved share my headaches faced while building a solution; doing so made it easy to re-read my thoughts before an interview or when I had to solve the same problem again months later.

My articles were, and still are, based entirely on real work experience but nowadays, it looks like we need to write just for SEO or positioning or ChatGPT Position 😭, not for returning real user value. The worst part is that we get more AI visitors than humans, and when a real human reads the article, they feel the difference.

Today, it often feels like we're trapped in a strange loop. Everyone is writing but increasing amount of "empty content" or "AI/Writer Slop." It has become a cycle where robots write for robots, and humans simply press "publish."

When we rely too much on these tools, we lose our unique voices. We stop being developers sharing real fixes and become just more noise in the crowd. To stand out today, I believe we must be more human than ever.

My Experience is My Best Asset

While AI can explain a library's API better than me, reading the full source-code and writing examples, it cannot tell you how it felt to debug a production issue at 2 AM or the scare of running a schema migration. The AI cannot create a unique analogy from scratch that connects with the reader.

I felt happy when, a few days ago, a colleague shared how much she loved my comparison of AI without MCP to a smart friend on the phone. It clicked because it was a direct reflection of my own experience—something I lived, rather than something a machine generated from a template.

Being writer doesn't require inflated phrasing like "delve into this transformative landscape." Instead, you just need to be yourself. My aim is to write for you as if we were having a coffee, telling you directly: "This is what I did, and this is how it worked for me."

Think of your article as a repository. You wouldn't add unnecessary dependencies, right? To keep my voice authentic, I always check my drafts for these points:

• Is this my story?: Did I actually try this code myself?
• Is my language simple?: Can a junior developer from any country understand me?
• Am I using real world examples?: This scenario case a real pain of my readers?
• Are my sentences short and direct?: Am I hiding a lack of clarity behind long words?
• Did I use a real-world analogy?: Can I explain this like I would to a friend?

Refactoring to a Human Tone

I know the AI is incredible, but it lacks the human touch. When I read some AI generated articles, I feel that they are empty; they don't have the soul of a real developer. Let's look at how I would refactor a typical AI-generated paragraph into my own voice.

How a Robot Writes: "Signals in Angular are pivotal to delve into the transformative capabilities of the new Angular signals to unleash the full potential of your application's reactivity."

How I Write: "Signals in Angular make my apps faster. They simplify how I handle data changes without the complexity of RxJS. Let's see how they work in a real project."

Did you feel the difference? The first line is boring without sharing experiences but with fancy, nice words, but they are empty.

But I love the AI

Yes, I use AI to help me write, but I use it to help me write better, not to write for me. I use it to help me find the right words, not to write the article for me.

I do a lot of typos and use incorrect verb tenses, so I use AI to correct them, but I always re-read the article to make sure it sounds like me.

The AI is perfect to help me with the boilerplate code, fix bugs, or suggest better approaches.

Final Reflections

This is not technical article, its just my feeling writing is about more than just data; it's about sharing a journey. Our real-world "headaches" are our most valuable lessons.

Please, if you like to write, just write.

• Write for your future self: Detail the difficult parts.
• Learn from others: As Mandy showed me, connection is essential.
• Stay authentic: Lived experience is something AI cannot replicate.

Take a paragraph you wrote recently and read it out loud. Ask yourself: "Does this sound like me?" If it doesn't, start cutting the fluff until your own voice begins to shine through.

Photo by VD Photography on Unsplash