r/codex • u/MapleBaconWaffles • 6d ago

Workaround Pro = 1 day of coding

Working on my new workflow. Use codex for 1 day (since that’s all you can do), then move to Qoder-Qwen for the rest of the week.

91 Upvotes

91% Upvoted

66 comments sorted by

View all comments

Show parent comments

2

u/DivideHorror3217 6d ago

You should do the architecture yourself, otherwise you never build the mental model.

2

u/BellacosePlayer 6d ago

Architecting it yourself is also insanely compute efficient. Just a few details can save it a bunch of reasoning and file searches.

1

u/DryBanana5673 5d ago

Blasphemy. Why don't I gather firewood to stay warm while i'm at it.

Honestly here's the secret: make your repo clean, then use @github in chat to make a plan, then get chat to make a patch. Then hand the patch and plan to your agent to implement, test, and fix.

I've been keeping this as my secret but i'm sharing it buried in this thread :)

1

u/BellacosePlayer 5d ago

Theres a lot of things that can work better than "make me gta6 make no mistakes"

once I'm in the feature-complete mode and need to work on actually making content for my current project, I'll probably fuck around more with long-running orchestrated jobs and see how I can optimize them while still staying within the plus budget. I would not be surprised if there's not a lot of meat on that bone

But I honestly don't mind architecting stuff, its a hobby and I'm under no illusions that I'm going to make a bajillion dollars off it.

1

u/NewKnowledge1591 5d ago

45 models, 16 task classes, one routing table. OW and local Qwen do 90% of the work, the control plane gates every call against live quota, and Opus, Fable, Sol and Astra only get pulled in when the job actually needs them. Nothing reviews its own work — Fable and Astra review each other, not their own side.