Posts

AI isn’t coming for your job. It’s coming for the lazy version of your job.

Most of what we call “work” is actually just filler. The emails, the templates, the boilerplate code — that’s not where your value lives. That’s just the stuff you do on autopilot.

In Episode 1 of BE MORE THAN AI, we’re digging into the “Lazy Version” of work, and why AI doing it better than you is actually the best thing that ever happened to your career.

Don’t compete with AI. Be the reason AI isn’t enough.

Watch the full breakdown below. 👇

Over the past few weeks, a growing narrative suggests that AI systems could soon perform work that traditionally required entire teams of researchers, engineers, or analysts.

These discussions highlight how rapidly AI capabilities are advancing.

Modern AI systems can search vast information sources, synthesize insights, generate code, and accelerate analysis at a pace that was difficult to imagine just a few years ago.

But many of these comparisons assume that knowledge work is simply a collection of tasks that can be automated.

In reality, enterprise work operates very differently.
It is not just about producing outputs.

It is about delivering reliable outcomes within complex systems. For example:

• Generating code is not the same as building production-ready systems with security, reliability, observability, and operational resilience.
• Producing research summaries is not the same as validating insights against real organizational data, constraints, and decision frameworks.
• Creating architecture diagrams is not the same as integrating systems across complex enterprise environments.
• Generating confident answers is not the same as establishing governance, accountability, and traceability.
• Running an AI agent is not the same as operating a system that must be trusted, versioned, monitored, and governed over time.

AI will undoubtedly compress large parts of knowledge work and accelerate research dramatically.

But turning outputs into trusted outcomes requires engineering discipline, domain judgment, and responsible oversight.

Because in real systems, the hardest part is rarely generating the work.
It is owning the consequences of it.

Enterprise Agentic AI is not a model play. It is engineered autonomy.

As model capabilities accelerate — larger context windows, stronger reasoning, embedded coding agents, automated security scans — the industry conversation continues to focus on performance gains.

But enterprise transformation does not occur at the model layer.
It occurs at the integration layer.

The latest edition of Technology Bytes explores why Agentic AI is predominantly an engineering discipline — and why integration maturity, agent identity, runtime governance, and cost control determine whether autonomy scales safely.

Models provide intelligence.

Architecture determines viability.

If you’re evaluating or building Enterprise Agentic AI, this distinction is not theoretical — it is structural.

Read the full edition here

Every technology wave expands before it refines. Agentic AI will be no different.

Cloud expanded before it matured.
Microservices scaled before governance caught up.
Data lakes grew before lifecycle control became necessary.

Agentic AI is now in that expansion phase.
More agents.
More orchestration layers.
More reasoning depth.
More tools embedded into workflows.

But refinement is coming.
And refinement will shift the question from
“How intelligent is it?
to
“How well engineered is it?

Here are 6 realities that will define that shift:

1️⃣ Agentic AI is a systems engineering discipline.
Persistent agents interacting with memory, APIs, retries, validators, and other agents are not isolated components.
They form distributed cognitive systems.
Managing them requires architectural rigor — boundaries, contracts, observability, and lifecycle design.

2️⃣ Prompts accumulate silent technical debt.
Prompts don’t crash when complexity increases.
They keep running.
Edge cases get layered.
Constraints expand.
Instructions grow.
Over time, clarity reduces while token usage increases.
The system works — but intent becomes harder to trace.

3️⃣ Memory without lifecycle control creates drift.
Persistent memory improves continuity.
But without retention policies, relevance scoring, expiry rules, and compression:
Noise increases.
Old assumptions persist.
Context injection grows.
Drift begins quietly — and compounds.

4️⃣ Retry loops multiply cost invisibly.
Agents reformulate, retry, re-evaluate, and call tools repeatedly.
What appears as one response may involve multiple reasoning passes.
If reasoning depth and retry frequency are not measured,
cost, latency, and carbon intensity expand without deliberate design.

5️⃣ Multi-agent architectures introduce probabilistic dependencies.
Planner agents influence researchers.
Validators reshape outputs.
Tool contracts evolve.
These are not deterministic service calls.
They are probabilistic reasoning interactions.
Complexity compounds quickly.

6️⃣ A new form of technical debt will become visible — Agentic AI debt. Not legacy code debt. Not infrastructure sprawl. Agentic AI debt accumulates in:

• Expanding reasoning chains
• Unbounded memory
• Tool-call amplification
• Retry inflation
• Cross-agent coupling

The system doesn’t fail.
It drifts.
And drift reshapes predictability, cost structures, sustainability posture, and operational clarity.

Agentic AI will not reduce the need for engineering rigor.
It will demand more of it.

Expansion rewards speed.
Refinement rewards discipline.

The real advantage in the agentic era will belong to those who engineer intelligence with clarity, constraint, and long-term stewardship.

Excited to see Accenture named a Leader in The Forrester Wave™: IT Sustainability Services, Q1 2026.

Great to contribute to this evaluation and recognition, especially highlighting our external collaboration with the Green Software Foundation and the advancement of the Software Carbon Intensity (SCI) standard.

As the IT sustainability services market continues to evolve and mature, connecting strategy, compliance, engineering, and measurable impact is more important than ever — particularly with the rapid growth of AI and cloud-native adoption.

Excited about what’s ahead as we continue advancing green software and Green AI, making sustainability a core pillar of digital transformation.

As India’s AI Impact Summit 2026 reflects the scale of ambition shaping our AI journey, it also presents an opportunity to consider a structural question:

How do we scale AI without proportionally scaling cost, carbon, and complexity?

In the latest edition of Technology Bytes, I share my perspective on applying Lean Agentic AI principles in the Indian context — across infrastructure, silicon strategy, edge deployments, measurement (SCI), and ecosystem innovation.
At population scale, architectural decisions compound.

Lean Agentic AI ensures they compound in favor of efficiency, resilience, and long-term sustainability.

If you’re building, investing in, or governing AI systems in India, this edition is for you.
🔗 Read the full article in this week’s Technology Bytes.

#AIIndiaImpactSummit2026 #indiaiimpact #agenticai #leanagenticai LinkedIn News India

AI now works for AI.
And that changes the equation.

Look closely at what’s happening:
Build → Review → Deploy → Access.

You prompt AI to write code.
AI reviews it.
AI approves it.
AI deploys it.
Then personal AI agents consume the output and present it back to humans.
The loop is tightening.

AI initiates.
AI validates.
AI operationalizes.
AI interfaces.

Humans are still essential — but we are shifting toward holistic thinking, judgment, ethics, exception handling, creativity, and direction.

Two years ago, I wrote about a concept called CodeMaster in Beyond the Software Code: A Tale of Human and Generative AI Transformation.

CodeMaster wasn’t just a coding engine.
It was a force that blurred the line between creator and creation.
A system powerful enough to make programmers question their relevance, their identity, their purpose.

The story unfolds in a world where the destinies of human programmers and CodeMaster are inextricably intertwined — a high-stakes landscape of rivalry, redemption, and uneasy collaboration.

As you move through the narrative, you encounter thought-provoking ideas, gripping suspense, and unforgettable moments that challenge the boundaries of what becomes possible when humans and AI-driven systems unite.

What ultimately prevails?
Do humans discover a deeper sense of purpose?
Or does AI demonstrate capabilities beyond what we imagined?

When I wrote it, it felt speculative.
Today, the question feels closer than fiction.

Get your copy now for a weekend read : https://amzn.to/4roALru
And read till the end.
It might surprise you.

If you’re overseeing an Agentic AI roadmap, these ten principles can save cost, carbon, and complexity.

In the race to deploy autonomous agents, many organizations are quietly accumulating Agentic Debt — systems that are over-orchestrated, expensive to run, and increasingly hard to govern.

Engineering excellence in the AI era isn’t about how much autonomy an agent has. It’s about how much efficiency, restraint, and intent are baked into the architecture.

Here are the 10 Lean Agentic AI Principles for building production-ready, sustainable systems:

1. Managed Context – Large context is a liability when unmanaged. More memory ≠ more intelligence.
2. Right-Sized Models – Not every prompt deserves a 70B response. Use the smallest brain that gets the job done.
3. Streamlined Orchestration – Agent orchestration is not a playground. Every extra agent is a cost, a delay, and an emission.
4. Think Before Compute – Reflections aren’t free. Validate the need before asking an agent to “think.
5. Targeted Retrieval – RAG isn’t always right. Retrieve only when it’s truly needed.
6. Account for Hidden Emissions – Emissions don’t show up in logs, but the planet still pays for them.
7. Reuse as Reasoning – Don’t re-run. Re-think. Reuse is the new reasoning.
8. Judicious Tool Use – More tools, more problems. Every tool adds latency and risk.
9. Judgmental Memory – Memory isn’t a journal. Storing everything is hoarding, not intelligence.
10. Governance Over Autonomy – Agentic systems need governance. Left unchecked, autonomy becomes chaos.

A lean mindset doesn’t just reduce overhead.
It increases predictability, performance, and trust across the entire agentic stack.

These ideas are now open-sourced as the Lean Agentic AI Playbook:
https://lnkd.in/dp8KZVku. For deep dive , refer to my book - https://leanagenticai.com/

As personal AI assistants move beyond request–response interaction and begin operating across inboxes, calendars, files, and external services—often through familiar chat interfaces—they naturally start to form networks of activity. One agent triggers another. Tasks span time. State persists. Decisions compound.

This edition of Technology Bytes looks at this shift through the lens of Lean Agentic AI—a framework centered on Cost, Carbon, and Complexity as first-class design constraints for long-running, tool-using agents.

Using OpenClaw purely as an architectural reference, the piece explores:

• how agent runtimes differ from single model calls
• why memory, retries, and escalation shape long-term behavior
• how agent networks amplify energy and resource usage
• how Lean Agentic AI helps structure agents that operate continuously and responsibly

This is not about limiting agents.
It’s about understanding what changes once agents become part of everyday systems—and designing for that reality from the start.

Two years ago, I launched a book for kids called Little AI Explorer. It was an attempt to explain Artificial Intelligence not through code or complexity, but through stories, curiosity, and ethics.

The idea was simple.

If AI is going to be part of a child’s world, they should grow up understanding it, questioning it, and using it responsibly, not fearing it.

That journey has now taken a natural next step.

Today, Little AI Explorer has evolved beyond the book into a dedicated learning experience for young explorers. Along with the website, I am happy to share that the Little AI Explorer Android application is now live, with the iOS version coming soon. This makes it easier for kids, parents, and educators to explore AI together, anywhere.

Explore the website: https://lnkd.in/dN5E8jta
Book: https://amzn.to/4rvdF2g

What remains unchanged is the intent.

• Keep AI concepts simple and age-appropriate
• Encourage curiosity over consumption
• Introduce ethics early, without fear or jargon
• Help parents and educators start meaningful conversations about AI

As AI quietly becomes part of everyday life, early awareness matters.
Because values cultivated early last longer, understanding AI through the lens of ethical and responsible use is how we prepare the next generation, not just to use technology, but to use it well.

#AIforKids #ResponsibleAI #EthicalAI #CreativeLearning #Education #LittleAIExplorer

Credits: Video created using #google #gemini #veo

Stop waiting for the “AI replacement.” It’s not coming—at least, not in the way most people think.

I’ve been part of the technology transformation story since 2000.

I started with mainframe modernization—screen-scraping IBM COBOL applications running on CICS systems and rebuilding interfaces in Java. At the time, the message was clear: open-source systems would replace mainframes.

They didn’t. Mainframes evolved—and in many enterprises, became even more critical.

Then came BPM and SOA. Once again, replacement was promised. What followed was more pragmatic: systems became modular, interoperable, and easier to scale.

Then Watson won Jeopardy. It reshaped how we thought about machine intelligence. Yet it didn’t replace experts—it augmented decision-making where context mattered.
Then came the cloud wave.
“Data centers will disappear.
“On-prem is dead.

Neither happened. What emerged instead was choice, elasticity, speed, and a new operating model. Enterprises modernized selectively, not blindly.

Now we’re in the Generative AI wave.
The language feels familiar:
“Developers will be replaced.
“Software engineering is over.
“Vibe coding is the future.

Vibe coding is not software engineering. It’s an interface shift, not the discipline itself. And AI, like every wave before it, augments capability—it doesn’t remove responsibility.

The anxiety we see today isn’t really an AI story. It’s the result of inflated expectations, COVID-era over-hiring, and the belief that productivity gains would be immediate. Some bets worked. Many didn’t. That’s how transformation has always unfolded.

The only advice I can offer is this: pair bold technology bets with measured hiring decisions. That balance is what turns waves of change into sustainable progress.

I consider myself fortunate to have been part of this journey for over two decades—learning from each wave, helping lead transformation efforts, and preparing early for what came next.

I’ve lived through enough waves to know this:
Technology rarely replaces. It almost always refines.
AI is no different.

If history teaches us anything, it’s that the next phase won’t be about replacing humans—but about raising the bar on leadership, engineering, and decision-making. We will need more people, not fewer—just working differently.

That’s the real transformation ahead.

AI is not eliminating software engineering.
It is forcing a reset of what it means to become a software engineer.

The story being sold today is simple:
AI will replace developers.
That message fits neatly with the hundreds of billions being poured into models, data centers, and compute.

But inside real engineering teams, something else is happening.
Junior engineers are not becoming less important.
They are becoming different.

For decades, juniors were valued for writing code:
◉ Boilerplate
◉ First drafts
◉ Simple bug fixes
◉ Pattern copying
◉ “Why doesn’t this compile?” work

That is also how many senior engineers in the industry today were trained.
Sitting next to someone more experienced.
Breaking things.
Fixing them.
Understanding why something failed.
That apprenticeship is what turned juniors into people who could own systems.
AI now produces that output instantly.

So the contribution that used to define a junior role has vanished.
Not because engineers are no longer needed, but because the old definition no longer fits an AI-assisted world.

There is another uncomfortable truth behind this.
AI is extremely good at routines.
It struggles with novelty.

It can generate what it has seen before at scale.

The moment something is ambiguous, new, or genuinely inventive, reliability drops sharply.

Expecting future engineers to simply “write the same code faster” misses the point.

The value is shifting away from repetition and toward judgment.

The mistake is to conclude that juniors are obsolete.

What actually needs to change is the expectation.
The new junior engineer is not measured by how much code they write.
They are measured by how well they:
◉ Review AI output
◉ Spot logic gaps and edge cases
◉ Test what the model confidently gets wrong
◉ Integrate AI code into real, messy systems
◉ Understand why something works or fails

They become the quality layer between models and production.
That is not a downgrade.
It is a more responsible role.

• Instead of learning syntax through repetition, they learn systems through validation.
• Instead of copying patterns, they learn critical evaluation.
• Instead of writing boilerplate, they learn to catch subtle failures hidden inside seemingly perfect code.

This requires a new core skill: paranoid reading.
◉ Not looking for obvious bugs
◉ Looking for things that look too clean
◉ Code that handles the happy path perfectly but ignores the real world
◉ Error handling that catches everything but explains nothing

This is harder than writing boilerplate.
It is also far more valuable.

If organisations make this shift deliberately, they get a generation of engineers who understand systems more deeply, not less.

If they do not, they will spend the next decade wondering where their senior engineers went.

Because you cannot grow seniors without juniors.

And you cannot grow juniors by having them rubber-stamp AI output they do not truly understand.

Green AI is typically framed around carbon reduction and energy efficiency.
That framing is necessary — but incomplete.

Most initiatives start with measuring emissions, improving energy efficiency, or selecting cleaner infrastructure. Those are foundational.

What often goes unexamined is why the energy is consumed in the first place — and how system design quietly amplifies or suppresses that demand.

From that lens, Green AI becomes more than efficiency tuning.
It becomes a discipline of how intelligence is designed, deployed, and allowed to operate at scale.

Once AI moves from experimentation to embedded decision-making, cost and carbon are no longer driven by individual model choices. They are shaped by how intelligence behaves across real workflows — how it plans, escalates, remembers, and decides when to act.

This is where Green AI stops being an abstract goal and starts showing up in concrete design patterns that repeat across systems.

1. Intelligence has a lifecycle, not a moment
   Impact accumulates across planning, execution, retries, memory, monitoring, and evolution.

2. Cost and carbon are shaped before the first token is generated
   Architecture, orchestration depth, memory, fallbacks, and verbosity define the footprint long before inference runs.

3. Efficiency is not minimalism, it is proportionality
   Using smaller models everywhere is as flawed as using large ones everywhere.
   The goal is proportional intelligence: capability scaled to consequence.

A quick classification or summary task does not need the same intelligence budget as a decision that can trigger a financial transaction, workflow change, or human intervention.

4. Carbon follows behavior, not infrastructure
   System behavior — escalation, interruption, memory, autonomy — determines emissions more than the stack itself.

5. Cost reduction is a byproduct, not the objective
   When intelligence is well-scoped, carbon drops naturally and cost follows.
   In practice, the challenge is no longer making AI intelligent.

It is ensuring that intelligence is exercised with intent and restraint at scale.
That is where Green AI becomes real.

Excited to see the Green Software Foundation’s 2025 Annual Report and the momentum behind this work.

I’m fortunate to lead multiple initiatives across the GSF — including the Standards Working Group, SCI for AI, and the Impact Framework — and it’s been incredibly rewarding to see how far this work has come over the past year.

What really makes this powerful is our vibrant, global community, working together to turn shared standards into real, measurable environmental impact.

Huge thanks to the Steering Committee, project teams, and everyone across the Green Software Foundation for the collaboration, energy, and momentum behind this.

Looking forward to pushing this even further together in 2026. 🌍🚀

Code generation is easy. Building a production-grade AI system is not.

The latest Technology Bytes shares a real-world experience from building an AI Life Coach — what breaks when LLMs move from demos to production, why system thinking matters more than prompts, and where engineering judgment and responsibility show up in human-facing AI.

If you’re working with LLMs beyond experimentation, this may resonate.

If AI is making feeds “smarter,” why do YouTube and LinkedIn feel more repetitive than ever?

The real question is simpler: Are you actually learning? Or just consuming?
The issue isn’t volume. It’s value.

There’s more content than ever, yet fewer moments of genuine insight. Scroll for a while and the patterns repeat:

• Familiar ideas, lightly reframed
• Advice optimized for reach, not depth
• Recycled narratives with new hooks

What’s being optimized isn’t learning. It’s attention.

The first wave of AI-powered feeds optimized for metrics: Clicks, watch time, replays.
But engagement is not the same as understanding.

Algorithms crave momentum, not nuance. The result? Feeds that feel busy—but don’t move you forward.
Time gets consumed. Perspective stays static.

That’s why the next shift won’t come from generating more content. It will come from value-led curation.

People (or purpose-built agents) who filter for:

• What actually teaches
• What adds context
• What justifies your limited attention

The platforms that matter won’t just capture time.
They’ll justify it.

AI can distribute content.
AI can scale reach.

But wisdom requires judgment.
And judgment remains human.

What AI was in 2025 — and what it becomes in 2026.

2025 was the year many assumptions around AI met reality.
Not in labs or demos, but inside real systems—codebases, workflows, agents, and production environments.

This first Technology Bytes edition of 2026 reflects on that shift:

• Why LLMs, GenAI, and agentic tools changed how software is built
• Why prompting was never the hard part
• Why model upgrades, drift, governance, and resilience now sit at the core
• And why AI increasingly needs to be treated like any other production software—designed, tested, deployed, and operated with discipline

The full blog looks back briefly at 2025, then focuses on what genuinely changes in 2026 for teams building and running AI systems end to end.
📖 The full piece is published as the latest Technology Bytes edition.

Thank you to everyone who continues to read and share Technology Bytes.
Wishing you a thoughtful and focused start to 2026.

AI doesn’t take control loudly.
It takes control quietly—one micro-choice, one nudge, one unseen influence at a time.

Most people think AI is a technical problem.
It isn’t. It’s a human story we still don’t fully understand.

We can keep building bigger models, faster transformers, smarter agents—but none of it matters if we don’t see how they reshape identity, intention, trust, fear, ambition, and the quiet ways technology rewrites us while we’re not looking.

AI doesn’t change the world through code.
It changes the world through narrative—through the stories we accept without question.

And stories are how we uncover the things we can’t measure:
the subtle shifts in purpose, the invisible pressures, the ethical awakening, the psychology behind “intelligent” systems.

To celebrate the holidays and spark deeper reflection, my entire four-book AI Novel series is FREE worldwide for the next 5 days.

🎁 Start reading ($0.00 on Amazon):
Silent AI | The Perspective on Influence
What happens when your choices are no longer your own?
👉 https://amzn.to/49sa7Yg

Beyond the Software Code | The Perspective on Transformation
Will the AI “CodeMaster” replace you—or force you to rediscover your purpose?
👉 https://amzn.to/3KQ1z4d

Echoes of Tomorrow | The Perspective on Responsibility
A 2045 world forced into an ethical reckoning. (Golden Book Award Winner 🏆)
👉 https://amzn.to/48ZAenW

Deceptive Success: The Master Mind | The Perspective on Psychology
When AI understands your mind better than you do—is it empathy or manipulation?
👉 https://amzn.to/4j900uE

Download them, read them over the holidays, and if any of the stories resonate, a short Amazon review helps them reach more readers.

Happy holidays, and wishing you a reflective and meaningful start to the new year.

Our last Technology Bytes newsletter of the year looks at how AI met reality in 2025—and what engineering will demand in 2026.

From AI excitement to engineering reality, this edition shares six clear predictions informed by what became visible in 2025—behaviour, failure modes, trust, cost, and the role of people as the real asset.

Thank you for reading Technology Bytes this year. Wishing you a calm close to 2025 and a focused start to 2026.

Happy to share the SCI for AI specification from our Green Software Foundation

As AI systems moved beyond traditional software patterns with model training, inference, and increasingly agentic behaviours, it became clear that existing software carbon metrics needed careful extension to remain meaningful. Measuring AI emissions is not just about more compute; it is about different lifecycles, boundaries, and usage patterns.

Within the Green Software Foundation’s standards work, SCI for AI emerged as a focused workstream to address these gaps by extending the ISO Software Carbon Intensity (SCI) framework for AI specific scenarios. This work has been shaped through focused workshops with 20+ member organisations early this year, followed by sustained weekly working sessions that helped turn ideas into a concrete, implementation ready specification.

The outcome reflects the strength of an open and inclusive community, where collective intelligence and diverse perspectives turn complex problems into practical, implementable standards. Sincere thanks to all the members who participated and shaped this specification, and to the member organisations whose contributions made this work possible.

As a next step, the community is inviting case studies for SCI for AI implementation. If you have existing AI systems or use cases and want to measure the carbon impact of your AI workloads and identify reduction opportunities, do reach out. Real world implementations will help validate and strengthen the specification.

Check out the details and the full specification at
👉 https://lnkd.in/gkvZeMm5

Grateful to be leading this effort alongside such a committed community.