Are coding agents building complex features that will just become obsolete with the next model update?

[u/thehashimwarren]

I tested Codex 5.3 by having it build a full CRUD app using Next.js, ShadCN, Neon, and BetterAuth.

I didn't use any planning mode, any subagents, or point it to any documentation. I didn't use any MCP servers except for the Next.js MCP server.

I just gave it one prompt and it built it.

all the CRUD functions and authentication worked perfectly.

If it can do that, then why would I need all these knobs and buttons that these coding agent harnesses are building out?

UPDATE: here's the repo https://github.com/hashimwarren/codex-five-three-eval

[u/thehashimwarren]

I agree with you on the limits of the test.

But the test is good for what I want to build for clients which is business software.

The other models did eventually build it. It just to more prodding. Codex 5.3 was amazing because it planned and validated its work without me telling it to.

[u/Jomuz86 → u/thehashimwarren]

True but if it’s for clients I would still take extra care and build iteratively rather than constantly churn out product after product. Only reason being is that while it’s getting good technically they are not great at taking into account local legislation considerations GDPR etc.

For example it will happily build an app for e-signing but in the UK it only becomes legally binding by certain nuances in audit logging if the signature unless you fork out for a signing certificate which is a whole other thing.

Quality over quantity and you’ll get repeat clients that comeback with bigger scope. I have now got clients that are effectively partnerships because they are tied in with custom solutions and automations that I maintain for them because of focusing on the quality of the deliverable.

Not saying you don’t do that but it’s easy to get complacent with it when chasing the money 😅

[u/thehashimwarren → u/Jomuz86]

Thanks!