dax routes architecture questions to a Gemini subagent
One task type goes to a different model inside the session, and the reaction says more about Gemini's reputation than the workflow.
dax says his team now uses Gemini quite a bit, and the trigger is specific. Whenever they hit a tricky architectural problem, a complex system design question, or need to simplify something, they ask for a Gemini subagent. His verdict is narrow and unexcited. It is pretty good there, and he does not see it talked about much.
whenever we have a tricky architectural problem, complex system design questions, or need to simplify something we ask for a gemini subagent
The interesting part is the shape of the habit, not the model. This is not a harness switch or a migration. The main session stays where it is, and one category of work gets handed off to a subagent running a different model, then the answer comes back into the same thread. Architecture and simplification questions are a reasonable category to split out, because they are mostly reading and reasoning over an existing system rather than editing a lot of files, so a handoff costs little and a second opinion is worth something.
The reaction
dax followed up with the detail that makes the post worth reading twice. He wrote that Gemini's reputation is such that he has never received more accusations of being paid to post something. That is one engineer's account of his replies, not a measurement, but it is a useful signal about how the room currently treats anyone who says a Gemini result was fine.
There is prior disagreement here. Theo reported that Gemini hallucinated in more than 80% of the review runs he put it through, which we covered earlier. The two claims are not in direct conflict, since they are different tasks and different harnesses, but they do mark the spread of opinion. One person is using it as a design consultant inside a subagent, another was running it as a reviewer and did not like what came back.
What dax offers is a report from use, not a benchmark. If you want to copy it, copy the routing rule rather than the conclusion, and find out on your own codebase whether architecture questions are the task type where a second model earns its place.
gemini's reputation is such that i've never received more accusations of being paid to post this
Have the good opinion, not the loud one
One email a day. Under three minutes. What working engineers found out about coding with AI.