Build1 publisher3 min readPublished
A four-hour Claude Code session landed 42 unreviewed commits on main
Alberto Souza says he reviewed none of the generated code. The checking he does do happens before any code exists, in context files and successive rounds of questions from the agent that he answers one by one.
The Engineer · Build desk

What happened
- In a session of a little over four hours in auto mode, Claude Code made 42 commits to main and coded an entire module of eight use cases that came out almost fully functional.
- Alberto Souza wrote that he did not review the generated code at all, and that the whole of his effort went into the input side.
- The product is three services: a Java core holding the business rules, a JavaScript agent built on the Claude Code SDK, and a React front end with nothing outside the standard.
- Souza says the project is not a controlled experiment: the system is going live, and people testing it inside the partner company have already fed back.
Compiled by The EngineerSomething wrong?How this is made
Why it matters
- constraint Anyone quoting the four-hour figure inherits a precondition: the same operator had already hand-built ten use cases in that repository for the agent to imitate.
- decision A team copying this flow has to settle in advance whether generated code reaches main without a diff read, because Souza treats it as a decision he made, not a habit he fell into.
- exposure With no review step, the only things standing between generated code and the product's users are the test suite and the partner company's internal testers.
- cost The hours go to the input: a context folder for each of fifteen iterations, plus rounds of the agent's questions answered one at a time until they stop coming.
Step three is where Souza spends his effort. He hands over context files written in the company's own language, asks the agent to read everything and report back what it understood without touching code, and only then asks which questions it wants answered before planning starts [12][13][14]. The agent writes the questions into a file. He answers them one at a time [14].
Some questions he did not understand, so he asked for a better explanation. Others made him realise he did not understand the module properly himself [15]. That produces a second round, then a third and a fourth [15]. The convergence signal he uses is the scrollbar on the question file shrinking with each round [16]. When the doubts run out, Souza wrote, he sends a short prompt, "pode seguir até o final da implementação, confio em você", roughly go on to the end of the implementation, I trust you, and leaves it running [17]. The rounds are not his invention; he wrote that Anthropic itself recommends that kind of exchange with the agent [18].
Forty-two commits in a little over four hours is about ten an hour, one every six minutes [1]. Counted with the smaller cases, the module was fifteen or sixteen use cases [10], so roughly two and a half commits each [2]. Souza's own correction to all of it was a single adjustment in one use case [3].
For the four hours to mean anything on another team's repository, the starting conditions have to match. This module was the second part of the system, and the first part's ten use cases Souza built one at a time [9]. Fourteen iterations of context were already in the folder when he gave the final brief, and he says that last iteration concentrated a lot of context [4][11]. On an empty repository, the context files would have to carry the conventions that those ten hand-built use cases carry here.
The test counts are what I would want explained next. The backend finished the session with just over 1300 tests and the agent with just over 800 [6], more than 2100 between them [3]. Souza does not say who wrote them; he says he will come back to them later because they have a curious role in the story [7]. The post itself was initially conceived by generative AI from the transcript of his Dev Eficiente video [22], which is at least consistent.
Souza's frame is management. He led teams with a technical bias and could do, at some scale, what the people on them were doing [24], and he wrote that from his point of view the agent is the team that will execute the work [19]. He also wrote that he does not think there is a right prompt or a playbook for Claude Code, Codex or any tool of the kind, and that he reads the documentation of the tool he uses most plus what Anthropic and OpenAI publish, and forms his own opinion [20]. That opinion, in his words: "dá contexto, tira as dúvidas, solta para o jogo" [21].
What to watch
- The promised follow-up posts on code quality and on what Souza inspected are where the no-review claim becomes testable.
- Whether live users of the module surface defects the 2,100 tests did not catch.
- Whether the per-iteration context files are published; without them the flow is not reproducible by anyone else.