CIOs ready for another role-change as AI becomes agent of chaos — The Register

As software generates software and autonomous agents execute work, the CIO’s center of gravity shifts from building systems to governing outcomes.

We’ve been delegating so much stuff in the last 10-15 years… like moving the on-prem data centers to cloud providers… transforming manager’s roles from hardware acquisition and planning to contractual surveillance, FinOps, etc. AI will accelerate this but in a new direction.

Memory Is the Machine:

Apple did not win an AI race. Apple made a memory-architecture decision in 2020 that turned out to be the AI race, five years before there was an AI race.

Maybe we should stop focusing on Siri failures and, like Om Malik said, on the real story where Apple has a five year lead… which happens to make a big difference in an AI-distributed world.

Deleted a few dozens Shortcuts today. All sort of Shortcuts: simple ones, utility ones, more complex ones. Many of them aren’t needed anymore because of my AI usage. I’m curious to see how Apple will make the Shortcuts landscape evolve in the age of AI.

Sometimes I test a local LLM on my M2 MacBook Air, which isn’t very powerful for this task. After a few prompts, it gets quite hot.🌡️ A MacBook Pro, with fans, would handle it better. Now, think about millions of people prompting LLMs in data centers worldwide, with much more powerful models responding and consuming huge amounts of energy. No wonder some parts of the world are experiencing an energy crisis because of AI.

This morning, I realized that having a self-hosted version of n8n comes with some notable limitations. For example, with the SaaS version, you can link your n8n instance to a GitHub repo so you can use version control right in GitHub and manage issues and all that. More details from Claude AI:

n8n has a native Source Control feature (available in Enterprise / Self-hosted Pro plans) that connects your n8n instance directly to a Git repo: Push/pull workflows, credentials stubs, and variables to/from a branch Supports environment promotion (e.g. dev → staging → prod branches)

If Google’s Gemini will be the core intelligence behind the “new Siri” this fall, as per Google’s recent statement, should I begin exploring it to understand its personality? 🤔

I believe I decided to build my web apps at the right time¹, because if I did it now, it would take two or three times longer due to the current credits consumption rate enforced by Anthropic. I made a little tweak to my dashboard web app this morning, and I’m already at 36% for the current session. It’s really that bad. I wouldn’t pay 200$ a month to get more credits.

This morning, I realized that managing open issues and bugs on GitHub is advantageous: the more detailed each open issue is, the more effective it serves as a prompt when importing into Claude Code to initiate a new bug-fixing session. Claude Code can also close the issue at my request and link it to a specific GitHub commit.

I’ve been testing the latest release of the Claude Desktop app, and I must say, more than ever, I prefer integration to splitting features across many different apps. I’m also leaving the CLI behind for now.

For all my pending issues across my different Claude Code and web apps, I just realized I could (and probably should) use GitHub for issue tracking instead of Craft. Additionally, I could develop a web app to monitor and manage all open issues across my repositories!