It sounds like you’re still writing code by hand and reading and reviewing code.

For that any decent model from the past year will do.

If you want to forget how to write code and not read generated code, then you need a very good frontier model, ideally one from 6-12 months in the future.

This kind of opinion has been around for about 10 months now already, since Opus 4.5 and Claude Code initial release. It just shifts alongside models.

I used to read the code till around May. Now I don't. Instead I validate behavior. And have multiple LLMs verify that the code implements my handwritten spec.

MiMo 2.5/2.6, MuseSpark 1.3, DeepSeek V4/4.1 Flash and GLM 5.3 Flash are perfectly capable of following my spec and then poking holes in the implementation till there are none left.

> It sounds like you’re still writing code by hand and reading and reviewing code.

This is such a naive, baseless opinion.

Nowadays any AI coding assistant service supports or can be used with sub-agent orchestration frameworks.

If you are in the business of software factories, you can use the cheapest models and even local models to handle some if not all tasks in the orchestration chain.

Adding tests or executing tests (unit, integration, UI, you name it) doesn't require a cutting edge frontier model. Neither does refactoring. Neither does identifying call stacks. Neither does planning a changeset.

You have your specialized subagents, you put together a small orchestrator subagent that handles feedback loops and handoffs,and you throw it at tasks.

For the past couple of months, most of the code I write is not code per se, it's subtask orchestrators. And unlike the old "only Opus is passable" days, the cheapest models do get the job done.