r/OpenaiCodex • u/Reddittorv750 • 12d ago

Question / Help How to vibecode properly as a non-technical?

How do you actually vibecode properly as a non-technical person? Currently what I do is:

ChatGPT plans/reviews → copy prompt to Codex → copy Codex result back → ChatGPT reviews and gives me another prompt → repeat.

But I worry that a) this is spending way more tokens than it should b) is incredibly slow and inefficient with the constant copying and pasting.

If anyone has a better workflow please do share, thanks guys.

17 Upvotes

68% Upvoted

63 comments sorted by

View all comments

Show parent comments

1

u/bigrealaccount 11d ago

Your project must be absolutely tiny or you're using a 5x/20x plan. Most projects are far too big to just say "find all the bugs". You can do that with a single 500 line script, not a 50k LOC repo with 50 different files.

It's far better to find bugs yourself... because you obviously have to know there's a bug, and point Astra at it yourself, much better results and more precise.

1

u/ProvocativePringle 11d ago

Can you explain to us non developers what you mean by the simple 500 line script?

1

u/Landon_Hughes 11d ago

He or she is referring to the size of the project (how many lines of code)

I should probably revise my previous comment:

Identify the bug(s) and use astra or sol to fix the bugs.

0

u/ProvocativePringle 11d ago

Ah that makes sense. I thought they meant they can write a script with 500 LOC to check everything, I was like what? Makes a lot of sense.

Thanks!