Software engineer here. Been professionally writing code since 2008 fulltime. I only started using AI this March. 5x Max plan since the first evening. Mind was blown. First thing I did was setting the processing verb to “Processing”. Anything else felt like a distraction. I was using Claude successfully and happily, 3-4 sessions in parallel in Tmux (my dev env for >= decade), all day long. Claude just did its thing, at a reasonable pace, and I barely ever hit the usage limit.
- It made commits within seconds
- It answered technical questions within seconds
- it completed implementations within minutes. Ctrl+o would show its thought process, the files it read, results from sub agents, … Even if it was off-screen in Tmux, it worked. You hit ctrl+o, scroll up, you see the full process. RESIZING the Tmux window worked. It worked beautifully. I was impressed. Text rewrapped, tables resized or even rendered into those inline lists to fit, and it WORKED OFF-SCREEN. You could resize the terminal window and scroll up to carefully read the plan from the top. Opus 4.7 rolled around and ALL OF THAT IS GONE NOW. Claude has gotten frigging slow. Almost unusably slow.
- “commit this” => you wait a solid 30s
- “implement this plan” => you wait 45 minutes
- Resize terminal window? Say goodbye to a readable plan or previous output. Lines are interlaced and diffs are cut off.
- Ctrl-o does not show anything useful anymore, and most definitely not for anything off-screen.
- It now tells me shit like “almost done thinking”. What is the value in that?
- I hit the limit regularly DESPITE having learned to engineer context, use Opus for deep reasoning and planning, Sonnet for quick edits and implementation. And on top of that, it IGNORES INSTRUCTIONS. I’ve been doing a lot of network programming. Sometimes things hang. But I keep all my test suites under 10s (yes) so I know very quickly, without wasting my time. So far I’ve told Claude about a thousand times (and written to memory) that it should ALWAYS use short timeouts, like 10s or 15s. But no, within one implementation cycle he switches back to 30s, 60s, 5 minutes. WTF!!! Another thing: I’ve told him a billion times “NEVER AUTO COMMMIT!”. Either I do that manually or tell Claude to “commit x”. After a while, he starts auto committing again! I’ve been using /caveman mode a lot for brevity. Much easier to read, and saves tokens. But of course, he’ll just forget about that. Done with the implementation? WALL OF TEXT!!! And now the pinnacle of enshittification. HE CAN’T EVEN IMPLEMENT A SIMPLE, EXPLICIT PLAN ANYMORE! This ~200 line plan for a small refactor in a Rust project, consisting only of 2 phases. I even used a fresh session for the second phase. The plan EXPLICITLY called for “change signature of handle_input(&[u8]) to take Bytes instead of &[u8]”. What did Claude do? He added ANOTHER function handle_input_bytes(Bytes). When I noticed at the end (after an eternity, of couse), I asked why and he said he wanted to keep backwards compatibility. WTFFFFF!!! Backwards compatibility with what? It’s a new project! And I frigging HATE his eagerness to “ship”. He repeatedly tries to cut corners, leave out half the features that I SPECIFICALLY planned for, just to “ship v1 now, do X, Y, and Z in v2”. WTFFFF!!! THERE IS NO v1 or v2!!! IT IS MY JOB to plan releases, you money-wasting piece of garbage!!! I OFFICIALLY HATE ANTRHOPIC. YOU HAD SOMETHING GOOD with Claude (Opus 4.6). Now it’s a steaming pile of garbage that can’t even rewrap text after resizing the terminal window, can’t follow basic instructions, is FRIGGING SLOW, and keeps talking like some moronic project manager about “ship v1 now”. IT IS OFFICIAL, PROPER GARBAGE. submitted by /u/event666
Originally posted by u/event666 on r/ClaudeCode
You must log in or # to comment.