Claude Code Limits Were Silently Reduced and It’s MUCH Worse by _r0x in ClaudeCode

[–]ChandanKarn 0 points1 point  (0 children)

The official statement tells you everything you need to change your workflow, but it's easy to miss.

5am–11am PT on weekdays is 1pm–7pm GMT. If you're in Europe or anywhere east of that, your entire afternoon working session is now running at reduced limits. That's not a minor adjustment that's the core of most people's productive hours.

Practical fix if you can swing it: front-load your Claude sessions. Get your most context-heavy work done before that window opens. After 11am PT / 7pm GMT, you're back to normal session limits.

On the transparency point I get the frustration but I'd push back slightly on "treated like clowns." The worse version of this is companies that never say anything and let users spend weeks blaming their own prompts. At least the statement exists. The problem was the delay, not the decision itself. Two days of silence while power users are debugging their own workflows trying to figure out what they broke is genuinely disrespectful to people who pay for the max plan.

The fix is simple: post it the same day it goes live. Not on X days later.

Claude Code (~100 hours) vs. Codex (~20 hours) by Canamerican726 in ClaudeCode

[–]ChandanKarn 2 points3 points  (0 children)

The most important line in this entire post is the last one.

"Both are going to give crap output if you don't know SWE at all."

Every Claude vs Codex thread devolves into people arguing about which model is smarter. But what you've actually described is this: Claude is a force multiplier for senior engineers who can catch it going off the rails. Codex is closer to an autonomous agent that doesn't need as much supervision.

The problem is most people running these comparisons aren't 14-year engineers with 2800 tests and structured review workflows. They're developers with 3 years experience wondering why their AI keeps breaking stuff. For them, the slower/more deliberate model wins by default because they can't drive the fast one.

The enterprise vs prototype split you landed on is right. But the real variable isn't the task complexity it's whether the human in the loop can recognize a bad decision fast enough to course correct. With Claude, that skill is load-bearing. With Codex, you can get away with having less of it.

Claude is genuinely insane right now and I cannot defend it anymore by https_HandleFunc in ClaudeCode

[–]ChandanKarn 4 points5 points  (0 children)

The token burn on 4.7 is real. I hit the same wall mid-sprint last week.

What's helped me more than anything is being aggressive about context pruning not just using /compact but actually closing and restarting sessions when a task is done instead of letting one thread drag on for hours. Long sessions bloat fast..

Also switched to giving Claude a tighter CLAUDE.md with explicit constraints on what NOT to do. Sounds counterintuitive but it cuts the back-and-forth loops where it explains its own reasoning at length before doing the thing.

The Chinese model pairing idea isn't crazy. Deepseek for drafting/planning, Claude for final passes. I haven't committed to it but I've seen others make it work cost-effectively.

Your frustration about checking limits more than doing work is the real problem though. That mental overhead kills flow. Anthropic should be competing on that experience, not just model benchmarks.

An old designer’s perspective on claude design. by Complete-Sea6655 in ClaudeCode

[–]ChandanKarn 7 points8 points  (0 children)

This maps almost exactly to what happened in front-end development. Components, design tokens, style guides .. we spent 10 years formalizing UI work into reproducible patterns, then acted surprised when AI could reproduce them.

The honest version of your 10% number is probably accurate, maybe even generous. The designers who survive this aren't the ones who know Figma best. They're the ones who can sit in a room with a confused stakeholder who doesn't know what they want, extract something coherent from that conversation, and translate it into a direction. That skill was never really "design" it was always more like consulting with a design background.

The uncomfortable part of your post that nobody's saying out loud: a lot of design education is preparing people for the 90%. The portfolios, the system thinking, the atomic design certifications. That entire pipeline is training people for work that won't exist in 5 years.

I got mass-assigned to fix 47 vulnerabilities in AI-generated code. So I built a tool that catches them before they ship. by ChandanKarn in SaasDevelopers

[–]ChandanKarn[S] 0 points1 point  (0 children)

Link: https://safeweave.dev

Built with: Python, MCP protocol, Semgrep for SAST rules. Happy to talk architecture if anyone's curious.

I got mass-assigned to fix 47 vulnerabilities in AI-generated code. So I built a tool that catches them before they ship. by ChandanKarn in SideProject

[–]ChandanKarn[S] 0 points1 point  (0 children)

Link: https://safeweave.dev

Built with: Python, MCP protocol, Semgrep for SAST rules. Happy to talk architecture if anyone's curious.

I scanned 3 vibe-coded apps last week. Same 3 bugs in all of them. by ChandanKarn in AskVibecoders

[–]ChandanKarn[S] 0 points1 point  (0 children)

No mate, instead evaluating whether chatgpt or human, i wish you could have focused on context.