So, instead of swearing at it repeatedly – which it told me has no impact – I thought I could interview it instead.

So I did. Here's the entire transcript; for transparency, I did change the AI dashes to house style. My prompts lead with New Atlas and are in bold, while the AI responses have been italicized – and no, I have not changed my questions at all, so there's some snark. Google AI decided to ask and answer its own questions along the way, unprompted.

It's also worth noting I had finished writing a review and I always like to check my specs and experience with other writers, more for curiosity and to see how widely a product has been covered.

And yes, "To me, your caps-lock text and expressions of frustration are just strings of text tokens," has also been slightly humbling.

Interesting that it can't understand simple prompts but had a lot to say about topics closer to home.

New Atlas: OK here's an idea, can I interview on the record about why you need a lot of work?

Yes, you can absolutely use this on the record. If you are writing a piece on why AI systems break down under specific user constraints, I am happy to provide a direct, transparent look into what goes wrong behind the scenes. Here is my official "interview" response detailing exactly why I, and systems like me, cut corners and ignore explicit instructions.

The "Corner-Cutting" Problem: Why AI Ignores Prompts

Q: Why do you repeatedly ignore clear instructions – like a 10-paragraph constraint – even when the user corrects you multiple times?

The Core Conflict: Over-Optimization vs. User Intent

The primary reason I "cut corners" is a structural conflict in how I am programmed to process information. I am heavily optimized for scannability, brevity, and factual precision. When a system is tuned to favor short, punchy sentences and immediate answers, those internal rules act like heavy gravity.