Loading video...

Video Failed to Load

Go Home

non-technical guide to codex

70,445 views • 1 year ago •via X (Twitter)

10 Comments

Admire The Web's profile picture
Admire The Web1 year ago

Now I know as a developer there is no need for codex. For concurrent tasks you need to niche down so you don’t get into conflicts. Even as a developer I wouldn’t be tasking codex to code on the same area of the app. Conflicts can take time to resolve and if you’re concurrent prompting then it’s mainly to save time which would then be lost in solving conflicts..

Ben Tossell's profile picture
Ben Tossell1 year ago

same issue with cursor's background agents

PrimeRadiant's profile picture
PrimeRadiant1 year ago

OpenAI should add sequential task processing, async just leads to conflict hell / breaks the workflow.

JJ Englert's profile picture
JJ Englert1 year ago

thanks for putting this together!

Moes's profile picture
Moes1 year ago

really clear, thanks. loved the part: "don't want to touch that, bc I can't code - so let's run it again" haha

Ben Tossell's profile picture
Ben Tossell1 year ago

happens a lot day to day 😂

Josh Gonsalves's profile picture
Josh Gonsalves1 year ago

The whole codex workflow seems pretty inefficient. How did you find using it compared to some of the other options out there (cursor, v0, lovable, bolt, etc)

Ben Tossell's profile picture
Ben Tossell1 year ago

for ui stuff its so annoying, cant upload anything. so i did a lot of the design work in v0 for my personal site tbh i like that there feels like less to deal with and code is truly in the background

Jeremiah Krakowski's profile picture
Jeremiah Krakowski1 year ago

Thanks dude

Vaibhav A's profile picture
Vaibhav A1 year ago

Thanks for putting it up together, really helpful and concise!

Related Videos