Genuinely curious about this rather than trying to make a point. Most Claude Code discussion I see is about workflows and day-to-day usage, but I haven’t seen much on how it behaves when you change your mind on the spec partway through - not “add a feature,” but an actual pivot where earlier architectural decisions stop making sense. Does it push back and re-architect properly, or does it try to preserve as much of the old code as possible even when that’s the wrong call? Context: I’m running Grevix AfterCode, a 24-hour solo hackathon where builders get an unexpected Challenge Card mid-event that forces exactly this kind of pivot. If you’re a heavy Claude Code user, what do you think would break first when the ground shifts under a build like that? submitted by /u/Significant-Log-4272
Originally posted by u/Significant-Log-4272 on r/ClaudeCode