Everyone Wants AI. Nobody is Doing the Math.

I've been job hunting recently.

Almost every job post mentions AI. Not because the company has a real plan
for it. Not because they've figured out where it actually fits. Just because
it's 2026 and it feels embarrassing not to say you're using AI.

That's the first problem. But it goes deeper than hiring trends.

The chatbot nobody asked for

Every company wants AI to do their daily work twice as fast. For example,
some companies I came across had already replaced their entire support team
with a chatbot.

On paper: cheaper, always available, scales easily.

In practice? It hallucinates. Gives wrong answers confidently. The user asks
something slightly outside what it knows and gets a response that makes no
sense. No fallback. No human. Just a confused user who closes the tab and
never comes back.

The problem wasn't the AI. It was bad design. Nobody thought about what
happens when the model doesn't know. Nobody built a way out to a real person.

They just shipped it because it felt modern.

And every one of those dead-end interactions spent real tokens. API calls
aren't free. Burning money on confusion isn't efficiency - it's just
expensive failure.

Nobody is doing the math

A company AI setup - Copilot, ChatGPT Enterprise, Claude API, internal
tooling - adds up quietly. And it still needs someone experienced to review
everything it generates, guide it, and fix what it breaks.

You didn't save a salary. You just moved the cost somewhere less visible.

Data centers have always used water. AI just made it worse.

Every server needs cooling. Cooling needs water. Emails, YouTube, Google
Search - all of it has always had a water cost. That's not new.

What changed is the scale. An AI response loads a massive model, runs billions of calculations, generates every word one token at a time - millions of times a day.

Email is a bicycle. Google Search is a scooter. An AI chatbot is a car.
Training a new model is a flight. All burn fuel. Just at completely different
levels.

A UC Riverside study found that a simple 100-word ChatGPT response consumes
roughly 500ml of water - about a full drinking bottle. That includes the
water used to cool the servers and the water burned to generate the
electricity powering them. 10 to 50 queries? Around 2 litres gone.

Training GPT-3 alone consumed an estimated 5.4 million liters of freshwater.
GPT-4 is bigger. And every company rushing to build their own model,
fine-tune it, redeploy it - they're all adding to that number. We're not
talking about a leaking tap. We're talking about a river being quietly
redirected.

What's happening right now

In March 2026, residents of Hanover County, Virginia protested a 427-acre
data center project. Not activists - regular people who saw the impact coming.

Meanwhile in Visakhapatnam, Andhra Pradesh, Google and Reliance are both
planning major AI data centers. People here are excited. Jobs, investment,
development. I understand why.

But Vizag already has low groundwater availability. These aren't small server
rooms. When groundwater levels drop, farmers in the surrounding region face
higher irrigation costs, lower yields, and direct competition with a data
center for the same water. That conversation isn't happening loudly enough
in India.

Why is a developer writing this

Because we're the ones building these systems. Most technical conversations
stay inside the system boundary - performance, latency, cost per query. But
we're building inside a physical world that has actual limits.

This isn't against AI. I use it. I write about it. I think it genuinely
changes what's possible.

But there's a real difference between using something thoughtfully and
slapping it onto your product because a job post told you to.

Between 2026 and 2040, most workflows will probably run on AI agents. Every
company will monetize it. That's likely going to happen.

Just plan before you build. Ask what it actually costs - not just in tokens
and API bills, but in the things that don't show up on a dashboard.

Food comes from agriculture. Agriculture runs on water. No amount of compute
fixes a drought.

If this made you think, drop a 🧡