正在加载视频...

视频加载失败

non-technical guide to codex

70,445 次观看 • 1 年前 •via X (Twitter)

10 条评论

Admire The Web 的头像
Admire The Web1 年前

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 的头像
Ben Tossell1 年前

same issue with cursor's background agents

PrimeRadiant 的头像
PrimeRadiant1 年前

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

JJ Englert 的头像
JJ Englert1 年前

thanks for putting this together!

Moes 的头像
Moes1 年前

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 的头像
Ben Tossell1 年前

happens a lot day to day 😂

Josh Gonsalves 的头像
Josh Gonsalves1 年前

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 的头像
Ben Tossell1 年前

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 的头像
Jeremiah Krakowski1 年前

Thanks dude

Vaibhav A 的头像
Vaibhav A1 年前

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

相关视频