upvote
1. When and how would gcc go down?

2. How often do you think that happens, compared to Claude?

reply
You 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.
reply
We're explicitly not talking about local models here; we're talking about Claude.
reply
Because 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.
reply
The 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

reply
What 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.
reply
Brother, look at the first comment in the chain you replied to. It very specifically was about Claude.
reply
Well, in that case, it's also very specifically about this guy's codebase, so none of us can really say anything on this.
reply
GCC down? Did the AI rotten your brain that much?

How can you come up with such non sense.

reply
The same thing as happens if I go to sleep for 8 hours.
reply
wat?
reply
Is this really a position you want to take in public with your real name and identity and everything plastered over your profile?
reply
What can I say, we can't all be geniuses.
reply