The Fantastic Four: First Steps | 🔗 imdb.com |
Set against the vibrant backdrop of a 1960s-inspired, retro-futuristic world. The Marvel's First Family (Reed Richards, Sue Storm, Johnny Storm and Ben Grimm) as they face their most daunting challenge yet. Forced to balance their roles as heroes with the strength of their family bond, they must defend Earth from a ravenous space god called Galactus and his enigmatic Herald, Silver Surfer. And if Galactus' plan to devour the entire planet and everyone on it weren't bad enough, it suddenly gets very personal.

Machine tags for this post:
movie:imdb=tt10676052, movie:series=Fantastic Four

⭐⭐⭐⭐

Saw Fantastic Four: First Steps in IMAX at Luxe Cinemas last night with Max. Really enjoyed it!

This one felt much truer to the 60s retro-futuristic aesthetic, which was a refreshing change. I thought it was a significant improvement over the earlier adaptations. The visuals, costumes, and music all felt new and distinct from other Marvel films.

Definitely a worthwhile opening weekend experience! The theatre went wild with loud cheers when Dr. Doom makes an fleeting appearance.

Luxe Cinemas

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

Epic Battle Between Lions, Black Mamba and Eagle! | 🔗 YouTube |
A snake eagle caught a black mamba, which then took over and got hold of the eagle. The eagle was trapped by the mamba and the mamba was stuck in the talons ...

I was perusing HackerNews today. Believe me, it is a good timesink. ⏳

I came across a link to a video titled: Epic Battle Between Lions, Black Mamba and Eagle!. Hoping I wouldn't be rickrolled, I watched the video. It was from Rietspruit Game Reserve, South Africa.

It opens with a rare and intense moment already in progress: a snake eagle caught in the grip of a black mamba. The eagle, clearly in distress, is trapped in the snake’s coils, an unexpected reversal of roles between predator and prey.

As the camera continues rolling, the situation grows even more complex. A pride of lions appears nearby, drawn to the scene. And then things turn interesting.

The entire encounter plays out with minimal interference from the people capturing the scene. And their off-camera commentary adds spice too.

👉 Watch the video here

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.

Mission: Impossible - The Final Reckoning | 🔗 imdb.com |
Our lives are the sum of our choices. Tom Cruise is Ethan Hunt in Mission: Impossible - The Final Reckoning.

Machine tags for this post:
movie:imdb=tt9603208, movie:series=Mission Impossible

⭐⭐⭐⭐

This felt like a documentary about the Mission Impossible series. The cuts from previous movies and a half-hearted attempt at tying up plots from the rest of the series was boring.

Tourist Family | 🔗 imdb.com |
A quirky Sri Lankan family seeking a fresh start in India transforms a disconnected neighborhood into a vibrant community with their infectious love and kindness.

Machine tags for this post:
movie:imdb=tt34915705, movie:language=tamil

⭐⭐⭐⭐

We had been talking about watching this movie in Chennai but never got a chance. Finally got around watching it in Kozhinjampara tonight in a nearly empty theatre.

Raviraj Theatre

Raiders of the Lost Ark | 🔗 imdb.com |
In 1936, archaeologists and adventurers of the U.S. government hired Indiana Jones to find the Ark of the Covenant before the Nazis could obtain its extraordinary powers.

Machine tags for this post:
movie:imdb=tt0082971, movies:series=Indiana Jones

⭐⭐⭐⭐

Max wanted to watch a movie now that we have a new AC.

I wanted to introduce some old classics.

Max's review: the climax was a bit gross (the melting faces)

On this day in 2002, I walked into my very first job at Angler as a Content Developer.

It was the beginning of a journey I couldn’t have fully imagined then, one shaped by learning, change, resilience, and growth. Over these 23 years, I've had the privilege of working across different roles and domains, each one adding its own layer of meaning and experience.

One thing that hasn’t changed is my curiosity. The same inquisitiveness that lit up my first day still drives me forward — to ask better questions, seek deeper understanding, and stay open to the unknown.

I've made my share of mistakes too, and I’m grateful for every single one of them. They’ve taught me humility, perspective, and the value of continuous reflection.

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.