Posts

I finished high school in Delhi in 1999. That year still sits somewhere in the background of everything that came after it. Not sharply. More like a low hum. The world felt like it was shifting, but nobody had a clear map of where it was going. Y2K was part of that atmosphere. Not in a precise way. More like background tension. Computers might fail. Systems might misread time. Something about the infrastructure of modern life felt slightly untrusted, even if nobody could quite point to where the risk actually was. ...

In the previous posts, I wrote about speaking at Global Azure ANZ 2026 and the strange speed at which universities seem to be reversing themselves on AI. But the conversation that lingered longest in my head afterwards was about coding itself. Or maybe not coding exactly. More about the feeling of coding. One developer told me they just were not enjoying the new AI coding tools very much. The outputs were fine. Useful even. But something felt missing. The satisfaction had thinned out somehow. ...

In my previous post, What I Learnt Speaking at Global Azure ANZ 2026, I mentioned a short conversation that stayed with me long after the event ended. A university student told me that in 2023 they had been actively discouraged from using AI during study. Minutes later, another student casually described using AI throughout nearly everything they worked on. Those two conversations happened back-to-back. And honestly, they captured something important about the current moment better than most keynote presentations do. ...

I went to Global Azure ANZ 2026 expecting cloud talks and AI demos. The talks were good. But the most interesting part of the event happened in conversations between sessions. I had the opportunity to speak at the Wellington chapter of Global Azure ANZ 2026, hosted alongside the Wellington Data Management and Analytics Meetup. Like many community events in Wellington, the atmosphere was relaxed, practical, and refreshingly free of corporate theatre. What stood out most though was not a specific demo or benchmark. It was the feeling that the industry has quietly crossed another threshold. ...

उलझे नहीं तो कैसे सुलझोगे, बिगड़े नहीं तो कैसे संभलोगे If you never get tangled, how will you learn to untangle? If things never go wrong, how will you learn to set them right? I was part of three AI trials inside a New Zealand government agency. All three gave us invaluable lessons. Out of those three, one progressed quite a lot, through four stages of development, and has shown genuine promise. ...

Your organisation has a document management system. Maybe it’s called Objective. Maybe it’s TRIM. Maybe it’s a home-grown records platform that nobody wants to touch because the person who built it left in 2014. Whatever it’s called, it holds years of institutional knowledge. Briefings, reports, decisions, correspondence, approvals. The kind of material that makes new work possible — if you can find it. You can’t. Not quickly, anyway. And that’s the problem this post is about. ...

Most companies don’t fail at AI because of bad models. They fail because they never had a strategy. That might sound blunt, but it’s what shows up again and again in enterprise settings. Teams jump into pilots, experiment with tools, hire a few data scientists—and then stall. Not because the tech didn’t work, but because the system around it didn’t exist. If you’re leading AI inside an organisation, you don’t need more tools. You need structure. ...

Your enterprise already has many channels. Humans use some. Machines use some. And now AI is asking for its own. In the last post, I explained why APIs are not enough and how MCP creates a new AI channel. If you missed that, read it here first: From APIs to AI Channels: The Next Evolution This post is the next step. We zoom out and see where this MCP channel actually fits. ...

Your system already has APIs. Documentation. Schemas. And yet an AI agent still can’t use it properly. That’s not a tooling problem. It’s a channel problem. For decades, every meaningful leap in software came from improving how we communicate with systems. It started simply. You’d walk over to someone’s desk. Ask how things worked. Knowledge lived in people’s heads. Fast if you knew who to ask. Painful if you didn’t. ...

After assembling the robot and working through the debugging in Part 2, the moment finally came. Power on. Motors twitch. Antennas move. And then… a small cheerful “phew phew” whistle. Reachy didn’t speak words. But in that moment it absolutely felt like a greeting. Kia ora. The First Boot — Kia Ora Aotearoa The first time Reachy powered up properly it made a small whistle-like sound while its motors calibrated. It isn’t speech. It’s just a sound effect the robot makes as it wakes up. ...