Hacker News Reader

> You're experiencing throttling. Use the API instead and pay per token.

That was using pay per token.

> Write every prompt like a government work contract in which you're required to select the lowest bidder, so put guardrails everywhere.

That is what I was doing yesterday. Worked fantastically. Today, I do the very same thing and... Nope. Can't even stick to the simplest instructions that have been perfectly fine in the past.

> If you're using Opus-4.5 for code generation, then consider using GPT-5.2-Codex for review.

As mentioned, I tried using Opus, but it didn't even get the point of producing anything worth reviewing. I've had great luck with it before, but not today.

> Instruct the model to keep a detailed log in a file and, after a context compaction

No chance of getting anywhere close to needing compaction today. I had to abort long before that.

> Build a mental model for which models are good at which tasks.

See, like I mentioned before, I thought I had this figured out, but now today it has all gone out the window.

View on HN

1. No, I didn’t form an outdated impression based on GPT-4 that I never updated, in fact I use these tools *constantly every single day* 2. Yes, I am using Opus 4.5 3. Yes, I am using a CLAUDE.md file that documents my expectations in detail 3a. No, it isn’t 20000 characters or anything 3b. Yes, thank you, I have in fact already heard about the “pink elephant problem” 4. Yes, I am routinely starting with fresh context 4a. No, I don’t expect every solution to be one-shotable 5. Yes, I am still using Opus fucking 4.5 6. At no point did I actually ask for Unsolicited LLM Tips 101.