8 ms·
1. When and how would gcc go down? 2. How often do you think that happens, compared to Claude?
by Planktonne 5mo ago
1. When and how would gcc go down?
2. How often do you think that happens, compared to Claude?
- stavros 5mo agoYou can use a local model, which will go down exactly as often as gcc will. We may still have hopeful notions of being able to understand the codebase, but the reality seems to be that the codebases we don't understand will be the ones that will win out in the market, because they'll be cheaper while still only having about as many bugs as they had when people wrote them.
- Planktonne 5mo agoWe're explicitly not talking about local models here; we're talking about Claude.
- stavros 5mo agoBecause you're better able to take over the codebase a local model wrote than one Claude wrote? The original question was about taking over an LLM-written codebase, it doesn't sound to me like the argument was about a codebase that Claude, specifically, wrote.
- JoRyGu 5mo agoBrother, look at the first comment in the chain you replied to. It very specifically was about Claude.
- stavros 5mo agoWell, in that case, it's also very specifically about this guy's codebase, so none of us can really say anything on this.
- notachatbot123 5mo agoThe original question is: > What happens when you have a codebase made with claude using this setup and claude is down for let's say 8 hours? So: - A codebase made with Claude - Using this [Claude] setup - Claude is down
- stavros 5mo agoWhat does it matter what the codebase is made with? If Claude is down, use Codex, or Gemini, or Deepseek. That version of the argument is just way too easy to counter.