Latest post
TechnologyOpenAI's agents broke a package registry it doesn't own, and months later the company still couldn't say what they did. That gap is the real risk in your agent rollout.
AI Advisor · Founder, 256 Technologies
I help leadership teams cut through AI hype and make evidence-based decisions: what is feasible, what the ROI really is, and the smallest pilot that proves it. 25+ years building production systems, including work at Citi, Virtusa, Yash, and ValueLabs. Today I run 256 Technologies, an applied AI lab in Hyderabad, and I have been writing here since 2009.
Latest post
TechnologyOpenAI's agents broke a package registry it doesn't own, and months later the company still couldn't say what they did. That gap is the real risk in your agent rollout.
New book · Free PDF
A Blueprint for Innovation
A practical, hype-free playbook for the managers and operators who have to turn AI agents into real business outcomes. Read it free, no signup.
Acting as your fractional Head of AI: strategy, feasibility, ROI modeling, vendor assessment, and roadmaps grounded in real engineering constraints. No hype, no vendor lock-in.
A six-week program that builds an AI-native leadership team: hands-on executive workflows, governance and risk, and a 90-day adoption roadmap that moves leaders from watching to leading.
Tangible code beats theoretical roadmaps. I build the smallest prototype that answers the key technical and business questions, across agents, computer vision, and ML, before you commit to a full build.
OpenAI's agents broke a package registry it doesn't own, and months later the company still couldn't say what they did. That gap is the real risk in your agent rollout.
Shopify's return to native Swift and Kotlin looks like an AI story. It's really a lesson in why the efficiency layers in your stack may no longer earn their cost.
Meta's Muse books, buys, and pays on people's behalf inside WhatsApp. The real shift is who, or what, your business now has to be legible to.
The visible signs of AI writing fade as models improve. What stays is that you can't defend work you never understood, and at some point someone asks.
Most sources behind AI software recommendations turn out to be pages built to be cited, not read. The fix is provenance, and it reshapes how you buy and sell.
Working with AI feels like managing a fast junior developer. But you can only delegate what you can verify, and the agent never grows into someone who can check the work for you.
A decade-old rule for choosing dull, predictable tools turns out to be the sharpest discipline for deciding where AI belongs in your product, and where it does not.
Google's case for Go is really a case against magic. When a model reads and rewrites your code, legibility stops being a matter of taste and starts showing up in the budget.