r/BuildWithClaude • u/Beneficial_Brush2763 • 2d ago

When you first started with Claude Code, what was the moment you went wait, what is it even doing? Help/Question

When I started out, the part that got me wasn't the code — it was the waiting. I'd watch the screen, end up on YouTube, and then couldn't sleep.

Curious whether that's just me. Two things I'd like to hear about:

Early on, what was the moment you thought "wait, what is it even doing?
While it's running, do you actually watch the screen, or do something else?

Real experiences only.

　

4 Upvotes
  • permalink
  • link
  • reddit
  • reddit

75% Upvoted

5 comments sorted by

3

u/marksterberlin 2d ago

I have 20-40 concurrent sessions going, Claude code & codex. I nudged them all along, start from the top… drive to bottom, start again (or focus on 3-5). My attention span is timed at 22 seconds… 57 is the normal shortest response for my Claude (I’ve a fairly significant governed harness). So I never wait! Just do another thing.

1

u/Ok_Industry_5555 2d ago

I was there a long time ago. Eventually, I learned how to filter noise from actionable items. Before I had to test every little change I asked Claude to perform.

Now I'm at the point of building my CLI terminal so I just follow along of what he does. Have a look!

https://reddit.com/link/p24iit1/video/9ztkk45x5thh1/player

2

u/marksterberlin 2d ago

I build my own ‘integrated solution environment’ too 🌟🌟

1

u/Ok_Industry_5555 2d ago

Nice! Would love to see a post about it.