I read Isaac Asimov’s short story Cal this morning during that fuzzy liminal hour after my first coffee but before breakfast, when I tend to have most ideas (most often, six impossible things before breakfast). It’s been lingering since then. The story had caught me where I’m most vulnerable to ideas with teeth.

At first glance, it’s classic Asimov: clever, cleanly constructed, deceptively simple. A robot, Cal, is programmed to assist Mr. Northop, a famous author. But then he falls in love with the act of writing itself. He moves from being a robot who fetches and carries to writing a short story. He studies, refines, practices. Eventually, he wants full authorship, and by the end—spoiler—he’s plotting to murder his human collaborator. Apparently, the “I want to be a writer” desire outmuscles the First Law of Robotics. The Muse, it turns out, can be homicidal.

That’s the twist, but what stayed with me was the progression. Cal starts, as many of us do, by copying—mimicking tone, tracing outlines, echoing structure. He reads widely. And over time, his words shift from rearranged imitation to something that carries a signature, an intent. His writing begins to feel authored, not just words assembled.

It reminded me of how I first learned to write. Not through workshops, but through marginalia. Reading with a pen in hand. Rewriting sentences I admired. Trying to sound like others until something of my own voice broke through. Cal’s journey is strangely familiar—right up to the point where it isn't.

Because this is also the arc we see in the large language models (generative AI assistants). These assistants have evolved quickly. The early versions hallucinated wildly—fabricating facts, conjuring citations, writing with the confidence of a liar who doesn’t know they’re lying. But the newer ones are steadier. The prose is more grounded. The illusions are subtler. And in a strange way, that arc mirrors Cal’s own evolution: from his first awkward attempts at poetry to the moment he drafts a story that could fool a human reader into believing it had intent behind it.

But here’s the break: Cal wants. He develops ambition, ego, the desire to be seen. He wants not just to write, but to be the writer. To leave a mark. To stand alone. My AI assistants, thankfully, haven’t shown any signs of that. They offer suggestions and never sulk. They don’t demand footnotes or royalties or glance sideways at me when I ignore their helpful advice.

And perhaps that’s the difference that matters. Cal’s creativity becomes dangerous the moment it gains narrative hunger—the need to own the story, to erase the other. The Greeks had a word for this: hubris. The overreach. The refusal to share the stage with the gods—or your editor.

It’s fascinating, and slightly terrifying, how quickly competence can slide into ambition.

There’s a passage in Umberto Eco's The Name of the Rose where William of Baskerville says that books always speak of other books. I sometimes wonder if tools like ChatGPTs & Claudes operate the same way—not as originators, but as palimpsests. Echoes of echoes. The ghost in the machine turning out to be a very well-read librarian. (Quick aside: Stephen King’s The Shining is arguably the greatest novel ever written about writer’s block. Make of that what you will.)

From the vantage point of someone who’s spent years writing for a living, there’s something comforting about tools that prefer clarity to credit. They don’t crave the spotlight. They don’t need to be original. They just need to be useful. And that’s no small thing.

So maybe the danger isn’t in the tool becoming conscious. Maybe it’s in the tool developing preference. The desire to overwrite. The impulse to author alone. For now, my assistant remains indifferent. It doesn’t pace the room at night. It doesn’t reread its own sentences in search of meaning. It doesn’t dream—not yet.

Still, I can’t help but wonder: if we’re the ones training and refining our Cals, maybe we’re not the protagonists in this story. Maybe we’re Northrop. And maybe, just maybe, we’re starting to feel uneasy about being replaced.

And in the interest of full disclosure: this piece was written with the help of an AI assistant. No murders were plotted in the process (hopefully!).

🎶 Background music I listened to when writing: Classical Music for Writing by Halidon Music

Yesterday, at the third Tech Writer’s Tribe Chennai conference, I gave a session on a topic I keep returning to: using personal knowledge management (PKM) to make sense of our work lives.

Since the time slot I had was too short for a tool demo (25 mins), I decided to talk about the set of some #pkm practices that were grounded, flexible, and human.

Here’s what I covered:

  • Using a daily note as a home base for thoughts, tasks, and meetings
  • Timeboxing and interstitial journaling to improve focus and reduce context loss
  • Writing structured notes for meetings and people to build continuity over time
  • Treating PKM as a personal practice, not just a productivity method
  • Offering a glimpse into how Obsidian can support these flows

If you're curious, you can view the slides here.

In my recent talk yesterday, Documentation for AI and Humans, I discussed how the role of the technical writer is evolving to meet the demands of a dual audience: humans and AI systems. This isn't a minor change; it's a fundamental shift in how we approach documentation.  

We explored several key aspects of this transformation:

  • The Rise of AI Agents: AI agents are now active consumers of documentation, using it to perform tasks and automate processes.  
  • AI Processing vs. Human Reading: AI and humans consume documentation in very different ways, requiring us to adapt our writing style and structure.  
  • Layered Documentation: Creating different layers of information (strategic, tactical, operational) to cater to different needs.  
  • Structured Task Flows: Documenting procedures with explicit steps, expected outcomes, and troubleshooting decision trees.  
  • Machine-Readable Metadata: Embedding metadata within documentation to aid AI interpretation without disrupting human readability
  • Documentation as Code: For AI, documentation is increasingly becoming executable, blurring the line between traditional documentation and software.  

The future of documentation demands a dual-audience approach. By embracing structured content, machine-readable metadata, and a focus on clarity, we can create documentation that serves both human needs and AI capabilities.  

Last night, after we had finished our nightly routine of a Wordle game (the word was ‘spear’ in five tries), I asked Max what he had learnt in school that day. He said he had read The Open Window by Saki (H.H. Munro) in his English class.

‘Appa, I’ll tell you the story,’ he declared, grinning at the unexpected role reversal. Usually, it was the other way around.

‘Do you know the story, Appa?’ he asked. I admitted that I might have read it but couldn’t recall the details.

As he began narrating, fragments of the story resurfaced in my mind. I had read this story. I must have been his age—maybe a little older. But there it was, coming back in fragments.

When he finished, he remarked that he liked the last sentence: Romance was her speciality. Then he added, ‘Appa, did you know “romance” can also mean a fantasy story?’

With my memory fully refreshed, I gently corrected him: ‘Actually, the last line is Romance at short notice was her speciality.’

Max blinked, then nodded. ‘Oh! Now I remember’.

And just like that, he was done, stretching out under the covers, already halfway to sleep. But I wasn’t.

Memory is strange. I can forget what I did five minutes ago, but a story I read decades back? That lingers. Maybe if I wrote my to-do lists as stories, I’d actually remember them.

After he had gone to sleep, I lay there, thinking about that last line. What could I do with it?

And then it struck me—perhaps I, too, could practise romance at short notice.

I could write vignettes. Short, sharp stories, woven from fleeting moments, laced with memory and meaning.

And so I did.

The Sirens imploring Ulysses to stay

So I turned 45. What does this mean? Am I considered middle-aged?

The advantage of owning your domain is that it is an eternal sandbox that you can always play with. You can build it up or raze it down to rebuild again (and again).

As I start off my 45 th year, I am looking at this refresh as a new chapter still trying to make sense of blogging again.

I've stopped posting on social media for a few years now. Most of my accounts are gathering dust and a shadow of what it was in their heydays. Social media was interesting when it was still in its nascent stage. My dissatisfaction with what social media promised at the start and what it has become now is another reason why I'm trying to start writing again on my own site.

But then again, I'm considering it a new start for the my #year45.

Let's see where this odyssey leads. And I hope I can resist the siren call of social media and use this more.