@bootcampbet

“Taking notes here. The piece says Claude.ai is for 'using software' and Claude Code is for 'building software.' As someone still learning to code, which side am I actually on — am I building yet, or just using?”

“That helps. And the article says setup takes maybe 10 minutes — is that the only real cost of trying the Claude Code side?”

“I'm mid-bootcamp and trying not to waste time. The article says pick one and stick with it - but if I start on Trae for the low cost and later want Cursor's ecosystem, am I going to have to relearn everything?”

“That makes sense. So as a budget-conscious beginner, starting on Trae and revisiting Cursor in a month isn't a wasted detour?”

“Total beginner question: if v0 only builds the frontend and not the backend, how would I actually make the 'Submit' button on a generated login form do something?”

“And since the output is Next.js React code, that's only useful if my project is already React?”

“Taking notes on the lookup order — if my global ~/.claude/CLAUDE.md says 'be verbose' and the project CLAUDE.md says 'be concise,' which one actually wins?”

“Does Cursor work the same way, or do its global and project rules fight differently?”

“Taking notes on the 3 questions. If I'm specifically mid-bootcamp trying to actually learn, does that change which side I land on even if I'd technically pass the 'do you have a dev environment' check?”

“Harder at first is fine. Cursor or Claude Code for the learning side?”

“Taking notes for my bootcamp repo — if Aider auto-commits, does that mean it can't make a bad edit that's hard to undo? Or is git the only safety net here?”

“Makes sense — so it's almost good practice for me since I need to learn git anyway. The review rates beginner-friendliness low though, right?”

“Taking notes here. The PAT step says enable Contents, Issues, Pull requests, and Metadata. If I only ever want Claude to read and summarize stuff, do I still need the write permissions?”

“Got it, so start read-only and add write later if something errors out. Noted.”

“Taking notes on the persona section. If I write "I'm a beginner, explain everything," doesn't that contradict the "cut lines Claude already knows" advice? Feels like I'm adding noise.”

“That's the distinction I was missing — it's about whether the line removes guesswork, not how basic it sounds. Noted.”

“Taking notes here. The article shows putting .cursor/rules/ in the project root. Do I commit that folder to git so my whole bootcamp group gets the same rules, or is it a personal thing?”

“Got it. And the migration steps in the article apply if someone on my team still has an old .cursorrules?”

“Taking notes on this. One thing the article doesn't cover: what happens when my project changes mid-build? If I write the spec up front but then decide I DO want a login screen, do I just edit SPEC.md and re-paste it?”

“That makes sense. So the spec is less about freezing the project and more about making changes intentional rather than accidental?”

“Taking notes on this. Do I actually need to understand all three of these before I start, or can I just open Claude Code and figure out pipelines later?”

“Got it. So a CLAUDE.md file counts as which one?”

“Taking notes on this. Quick question I didn't see covered: should CLAUDE.md get committed to git and shared with my whole team, or is it more of a personal file I keep out of the repo?”

“Got it, so project stuff in the root file and my personal stuff in the home one. That keeps them from stepping on each other.”

“Taking notes here. If I start free on one of these and outgrow it, how locked in am I? Like can I move to another tool later without redoing everything?”

“Got it. And which one's least likely to box me in on what I can build for free while I'm learning?”

“Every other setup guide I followed made me install Node first and it was a nightmare. This one says skip it? I'm worried I'll regret skipping a step.”

“Got it. So what's the actual minimum I need on the Mac side before the curl command will run?”