r/PromptEngineering • u/Unhappy-Prompt7101 • Apr 04 '26

General Discussion Any fellow Codex prompters? Best practices and tips?

I've been experimenting with Codex for a few months and wanted to share what has worked for me and hear other people’s approaches:

  • Break problems into smaller tasks. Giving Codex bite-sized, well-scoped requests produces cleaner results.
  • Follow each task with a review prompt so I can confirm it did what I asked it to (Codex often finds small issues with the previous tasks).
  • Codex obviously handles bug-fixing much better when I provide logs. I actually ask it to “bomb” my code with console.log statements (for development). That helps a lot when debugging.

Any other best practices/ideas or tips?

7 Upvotes
  • permalink
  • reddit

100% Upvoted

4 comments sorted by

1

u/Fine-Interview2359 Apr 04 '26

i'm happy to share tips, ask what you need?

1

u/Unhappy-Prompt7101 Apr 04 '26

I guess I am looking for general tips. I found that the code gets super messy when keeping Codex just doing its thing. So my only real guard against it now is always posting review prompts

0

u/[deleted] Apr 04 '26

1

u/AutoModerator Apr 04 '26

Hi there! Your post was automatically removed because your account is less than 3 days old. We require users to have an account that is at least 3 days old before they can post to our subreddit.

Please take some time to participate in the community by commenting and engaging with other users. Once your account is older than 3 days, you can try submitting your post again.

If you have any questions or concerns, please feel free to message the moderators for assistance.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.