Can AI Really Learn to Write Like Me?

For anyone who writes regularly, the rise of generative AI creates an interesting dilemma. AI can produce text remarkably quickly. It can summarize information, suggest headlines, rewrite paragraphs and help turn a collection of ideas into something coherent. But can it actually learn to write like you? That is the question behind a fascinating experiment by Feather in his blog post Teaching AI My Writing Voice. Instead of simply asking AI to generate more content, Feather tried to teach it something much harder to define: his personal writing voice.

More than copying a style

At first sight, teaching AI how you write might sound relatively straightforward. Give it a collection of previous articles and tell it to imitate them. But a writing voice is much more complicated than that. It is partly vocabulary and sentence structure, of course. Some writers prefer short sentences. Others use long paragraphs in which ideas gradually develop. Some use humour frequently, while others prefer a more factual approach. Some start almost every article with an anecdote or personal observation.

But voice is also about the choices behind the words. What do you consider important? What deserves an explanation? When do you add context? Which subjects do you approach critically? And perhaps equally important: what kind of language would you never use?

That is what makes Feather’s experiment so interesting. He isn’t merely trying to make an AI reproduce the superficial characteristics of his writing. He wants to see whether it can understand the patterns behind it. As he explains in his original blog post, the process becomes an exercise in defining what actually makes his writing his own.

AI as an apprentice writer

One useful way of looking at this is to think of AI as an apprentice rather than an automatic content generator. Imagine working with a new editor who has never seen your work before. Initially, that person might make perfectly reasonable suggestions that nevertheless don’t sound like you.

Over time, however, an editor learns. They discover that you dislike certain expressions. They notice that you prefer examples over abstract explanations. They understand that you don’t want every article to end with a grand conclusion. Eventually, they start anticipating your preferences.

Something similar can happen when working with AI. The difference is that we need to make many of those preferences explicit. And that can be surprisingly difficult. We often know immediately when a piece of text doesn’t sound like us. Explaining why is much harder.

Your archive becomes valuable

There is another interesting aspect to Feather’s experiment: the value of an existing writing archive. Someone who has been blogging for years may have hundreds or even thousands of articles online. Together, those posts contain an enormous amount of information about that person’s interests, language, opinions and writing habits.

Until recently, that archive was primarily intended for human readers. AI changes that. A collection of old blog posts can also become reference material for a personal writing assistant. Instead of starting every conversation with an empty AI system and explaining your preferences again, the technology could potentially learn from years of previous work. For bloggers and other people who write frequently, that is an intriguing possibility.

But imitation isn’t identity

There is an obvious limitation. AI can recognise patterns in writing, but those patterns are ultimately the result of something the AI doesn’t possess: a life. A personal blog reflects conversations, travel, work, mistakes, discoveries, books, music, people and countless other experiences. Those experiences influence how someone writes.

An AI can learn that a writer frequently connects technology with everyday experiences. It can recognise that personal anecdotes often appear at the beginning of articles. It might even become remarkably good at reproducing that pattern. But it didn’t have those experiences. That distinction matters, particularly with personal publishing.

A different way of thinking about AI

Perhaps that is also why Feather’s experiment points towards a more interesting role for AI in writing. The discussion around generative AI often focuses on replacement: can AI write an article instead of a journalist, blogger, copywriter or author? But that may be the less interesting question.

A much more useful question is whether AI can become sufficiently familiar with an individual writer that it can help that person write better and more efficiently without removing the personality from the result. It could remember previous stories. It could point out that you wrote about a similar subject three years ago. It could suggest connections between ideas. It could produce a first draft that already resembles your normal writing instead of delivering the familiar, polished-but-generic AI prose. The writer would still decide what is worth saying.

Making AI more personal

That is ultimately what makes Feather’s experiment worth reading. It turns the usual AI-writing discussion around. Instead of asking how writers should adapt themselves to AI, the question becomes: how can we make AI adapt itself to the writer? That sounds like a subtle difference, but it is an important one. The most interesting future for AI-assisted writing may not be a world in which machines generate enormous quantities of anonymous content. It may be one in which our tools become increasingly familiar with the way we think, write and communicate.

Not an AI that writes for us, in other words. But one that gradually learns how to write with us.

Just Me: How Hard Can It Be to Build Your Own Website?

I created Just Me myself. Is that complicated? Not really. Or perhaps I should say: it does not have to be complicated. If you have never created your own website before, the whole process can look slightly intimidating from the outside. Domains, hosting, databases, SSL certificates, themes and content management systems — there are plenty of technical terms available to make a fairly simple process sound much more mysterious than it actually is. In reality, most of it comes down to one thing: just doing it.

So, for anyone who has never built a website before, here is roughly how Just Me came into existence.

First, a name

The first step was obviously finding a name. Fortunately, I had already solved that problem. On LinkedIn I have been using Just Me as my “company name” for some time, simply because I work independently and the name seemed to describe that rather well. So Just Me it was.

That also made choosing a domain name relatively easy. The only question was the extension. Should it be .nl, .com or perhaps .eu? Then I came across .website. Well, if you are building a website called Just Me, justme.website seems almost impossible to resist. So that became the domain.

Hugo seemed like a good idea

The next question was what to use to actually build the site. For a while, I seriously considered using a Static Site Generator, and Hugo in particular. I still think the concept is very appealing. You write your articles in Markdown, generate the website and simply upload a new version whenever you publish something. Simple, lightweight and very much in the spirit of having your own small corner of the web.

Initially, things went surprisingly well. I had my first Hugo website running quite quickly. There was only one problem: I did not really like the theme. How difficult could it possibly be to install another one?

Uhm… apparently, quite difficult.

I selected another theme and suddenly found myself dealing with all kinds of technical issues. One problem led to another, and before long my nice little Hugo experiment had turned into a troubleshooting exercise. I have not given up on it, by the way. I still want to understand Hugo properly, so I will continue experimenting with it. But at the moment, the score is probably Robbert: 0. Hugo theme: 1.

Back to WordPress

Fortunately, there was an obvious alternative: WordPress. It is open source, I have worked with it many times before and I know my way around it reasonably well. So I logged into my hosting environment and installed WordPress. That took only a few minutes. Connect a database, create an account, choose a password and you are done.

Or so I thought.

When I tried to log in for the first time, Firefox complained that I was trying to use HTTP instead of HTTPS. Fair enough. Setting up SSL is easy, so a few minutes later that problem was solved. I tried again.

Wrong password.

That was strange, because I was absolutely certain I was using the correct username and password. By then it was getting late, so I decided to stop. Perhaps I had simply overlooked something. Tomorrow morning, with some coffee and a fresh brain, everything would probably work.

It did not. Same problem.

Time to call a human

My regular technical assistant, Mistral Vibe, came up with several potentially useful suggestions. They also went much further technically than I thought should be necessary. Surely logging into a freshly installed WordPress site could not be that complicated?

So I swallowed a little bit of technical pride and called the hosting company’s helpdesk. I had mentally prepared myself for a long wait, but two minutes later I was talking to an actual person. That alone already felt like a small victory.

He agreed that the situation was strange. I could hear some muttering and sighing at the other end of the line, and at one point he consulted a colleague. Eventually, he solved the problem by creating a new password for me. And suddenly it worked. There it was: WordPress, the dashboard and, most importantly, access to my own website.

Finally, I could start blogging.

Learning by doing

There was another nice detail. The support guy also explained how I could change that password myself if I ever needed to do so directly in the database. You have to dig reasonably deep into phpMyAdmin, which sounds much more frightening than it actually is. Once you understand roughly what you are looking at, it is quite logical.

And that is perhaps one of the main things I like about creating a website yourself. You do not need to know everything before you start. You learn things because you run into them. A domain teaches you something about DNS. WordPress teaches you something about databases. SSL teaches you something about certificates. And a stubborn Hugo theme teaches you patience.

Most importantly, you end up with something that is genuinely yours.

Just Me is now my own little place on the IndieWeb. A place where I can write about technology, digital autonomy, sustainability, music, space, personal knowledge management or whatever else happens to interest me that day. It does not need an algorithm, a publishing strategy or a social media platform deciding who gets to see it. It is simply my website.

And, appropriately enough, it is called Just Me.

in Tech | 902 Words

Why I Started Just Me

As a journalist, there are many subjects I write about professionally. Technology is an obvious one. So are cloud computing, data centers, cybersecurity, AI and industrial technology. But there are also many subjects that fascinate me personally and that do not always fit neatly into one of the websites, magazines or other platforms I write for.

That is one of the reasons I started Just Me. I wanted a place where I could simply write about the things I find interesting. And there are quite a few of those.

Technology, but not only technology

Technology will certainly be an important part of this blog. I have always been interested in new technologies and in the way they change the world around us. AI is an obvious example, but I am just as interested in developments around open source software, European technology and the growing discussion about digital sovereignty and autonomy.

I find it fascinating to look beyond the individual product or announcement and ask what a development actually means. Who controls the technology we use? Where is our data stored? How dependent have we become on a relatively small number of technology companies? And what alternatives are emerging?

Sustainability is another subject that regularly catches my attention. Particularly when it intersects with technology. Energy, data centers, renewable power, more efficient computing and smarter use of resources are all subjects I expect to return to regularly. European companies are actually at the forefront of developments like these.

Looking a little further away

I have been fascinated by spaceflight for as long as I can remember. And right now, space is becoming particularly interesting again. New launch companies, satellites, lunar missions, reusable rockets, space-based infrastructure and an increasingly important European space industry are creating an enormous number of stories worth following.

Space technology is also becoming much more closely connected to everyday life on Earth. Satellites help us understand climate change, monitor agriculture, improve communications and respond to natural disasters. At the same time, ideas that sounded highly futuristic only a few years ago are gradually becoming serious engineering projects. That makes space exactly the sort of subject I enjoy writing about.

Building my own knowledge system

Another recurring subject will probably be personal knowledge management. I read a lot. I save articles. I make notes. I bookmark websites. I collect ideas for future stories. And, like many people who do this, I am constantly trying to find better ways to organise all that information. That has led me to tools and concepts such as digital notebooks, knowledge graphs, linked notes, RSS, self-hosted services and personal archives. At the moment, I’m using Capacities.io for this. It has quite a steep learning curve, but I have to say: it really works for me!

I am interested not only in the tools themselves, but also in the underlying question: how do you build a useful collection of knowledge without simply creating an enormous digital pile that you never look at again?

Music, blogs and the small internet

Then there is music. I enjoy streaming, but I also like CDs, vinyl records and even cassettes. There is something interesting about the different ways in which we discover, collect and listen to music. Sometimes the technology becomes part of the experience: the crackle of vinyl, the mechanical sound of a cassette player or simply rediscovering an album you had forgotten about for decades.

The same is true for blogs on the indyweb. I have become increasingly interested in personal websites and independent blogs. In a web dominated by enormous platforms, algorithms and automatically generated content, there is something refreshing about discovering a small website maintained by one person who simply writes about things he or she cares about. One post might be about software development. The next about a record they bought. Another about a walk through a city, a book they read or a strange technical problem they finally managed to solve.

There does not always have to be a content strategy behind it. Sometimes somebody simply has something interesting to say.

A place for curiosity

That is roughly what I want Just Me to be. Not a tightly defined technology publication. Not a personal diary either. And certainly not a blog that tries to stay within one carefully selected niche. It is simply a place where I can follow my curiosity. One day that may result in a story about European technology or digital autonomy. Another day it might be about a spacecraft, a useful open source application, a personal knowledge management experiment, an interesting blog I discovered or an old record that suddenly sounds wonderful again.

There is plenty to write about. And that is exactly what I intend to do.