Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

non-technical guide to codex

70,445 Aufrufe • vor 1 Jahr •via X (Twitter)

10 Kommentare

Profilbild von Admire The Web
Admire The Webvor 1 Jahr

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..

Profilbild von Ben Tossell
Ben Tossellvor 1 Jahr

same issue with cursor's background agents

Profilbild von PrimeRadiant
PrimeRadiantvor 1 Jahr

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

Profilbild von JJ Englert
JJ Englertvor 1 Jahr

thanks for putting this together!

Profilbild von Moes
Moesvor 1 Jahr

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

Profilbild von Ben Tossell
Ben Tossellvor 1 Jahr

happens a lot day to day 😂

Profilbild von Josh Gonsalves
Josh Gonsalvesvor 1 Jahr

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)

Profilbild von Ben Tossell
Ben Tossellvor 1 Jahr

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

Profilbild von Jeremiah Krakowski
Jeremiah Krakowskivor 1 Jahr

Thanks dude

Profilbild von Vaibhav A
Vaibhav Avor 1 Jahr

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

Ähnliche Videos