> Claim that a data center is using 1000x as much water as a city of 88,000 people, where it’s actually using about 0.22x as much water as the city, and only 3% of the municipal water system the city relies on. She’s off by a factor of 4500. This is the single largest error in any popular book that I’ve found on my own, and to my knowledge I’m the first person to notice it.

Yeah, she might be wrong. But a data center also using 1/5th of the water consumption of an 88k person city should still be what are debating. We also have a base rate fallacy, we don't know know how well or how poorly they are using water. Nearly all criticisms of AI data center criticisms boil (no pun intended) down to yeah, but what about almonds or rice or xyz. That isn't a healthy way to adjust how we talk about data center water consumption.

It is a classic debate tactic. Someone makes an argument, then buttresses that argument with a number. You attack the number, pretending that you didn't just correct the number, but also invalidate the original argument. We shouldn't be using these tactics to talk about the tragedy of the commons.

I worked for a hyperscaler, I poked around a bit about water usage both internally and externally and it wasn't good. There was little to no thought other than, "we can pay X to have water delivered, doesn't matter if it sourced responsibly." (to glibly paraphrase, company policy is to never write the honest part down)

Look at how hard Google fought to not have water data released in The Dalles Oregon for their DC there. Many DCs are supplied by water that is meant for humans, sourced from aquifers that took hundreds of thousands of years to fill, that are being depleted faster than they are filled, already.

I think AI is powerful tool, but we still can't give DC expansion a pass.