I would say it is the responsibility of the CTO (whoever is responsible) to talk some sense into the CEOs (whoever in the exec team is having AI psychosis). Yes, yes—what if they themselves are having psychosis but that’s the point.
I had some questions in my mind about DCs using closed loop systems and read the article a little. In case anyone else also has similar thoughts:
—-
The company said its water consumption was so high last year because of temporary construction-related activities, such as concrete work, dust control and site preparation.
Once operational, the company said the data centers only will use water for domestic needs, such as bathrooms and kitchens. That will total the equivalent of what four U.S. households use per month, the spokesperson said.
That may not happen for another few years, however. The company is still actively building and expanding its Fayetteville data center campus. It aims to finish in three to five years.
I think the usage patterns of a lot of harnesses are pushing against their planned capacity. I would say they can certainly explain themselves a lot better.
There is that (you can still use coding agents on the other 80% to polish, by the way) but to me this situation underscores the value of a good "editor"--someone who says this is good to ship vs. not this not now.
Claude Code Team: Please fix the core experience instead of branching out into all these tertiary features. I know it is fun and profit to release new features but you need to go deeper into features not broader into there be dragons territory.
Honestly it is unclear to me still. Last month wrote a whole coding principles AGENTS/CLAUDE MD file but not clear if the produced code has changed _because of_ that or other reasons. Couple of things give me confidence that the models actually do read them and follow them.
1) I have a sentence that says: "I am your pairing buddy Bob. Occasionally address me by my name." And you will see them address you by the name, occasionally.
2) I do have per project "Project Tenets." Each tenets is a catchy couple of words, like Design for Agent First, Tolerant Interfaces over Robust Interfaces. If you notice the coding assistant referring to this you know they are aware, and they do sometimes refer to it. I also have a common list of principles but I think they are less useful because those are generic for software engineering.
3) Occasionally, I will do the following prompt:
i) Who am I?
ii) What is our design philosophy and tenets?
iii) Go through the repo and ensure the architecture and codebase adheres to our design philosophy and tenets.