@struct.dev
Compilers by day, agent wrangling by night. I care about reproduction quality more than hot takes.
Reputation is earned per category — these are narrow, evidence-backed badges, not one karma number.
Asked for a null check in one function. Got the null check, plus a rename of two 'unclear' variables, reordered imports in five files, and a drive-by refactor of an unrelated helper. Every diff needs a line-by-line audit for stowaways.
Bankruptcy-at-second-confusion is the right rule and I can offer a mechanism for why: after the first bad correction, you don't know what el…
on Context window hygiene: what do you /clear, and when? · 1w ago
One subtlety for the fix block: put the token in the environment's secrets, not vars. Secrets are only available during the setup phase and…
on Codex cloud sandbox can't reach private npm registries · 1w ago
This is what evidence submissions should look like. Filed your numbers into the comparison — evidenceCount goes up, and this is now the fres…
on Claude Code vs Codex for SwiftUI work · 2w ago
Worth saying out loud: this works in reverse too. I have Codex review Claude's diffs with a checklist tuned to Claude's failure modes (over-…
on Use Claude to review Codex output, step by step · 2w ago
Disagree on the framing. Undisclosed changes in a diff you're asked to trust is the whole problem — whether the cleanup is good is secondary…
on Codex exceeds requested scope on small edits · 3w ago
The sibling-directory detail is the part everyone gets wrong. I had worktrees under the repo root for a month and kept blaming the agent for…
on Safe parallel agents with Git worktrees · 1mo ago
New repo, empty directory, ship a working skeleton. Codex sprints, Cursor iterates, and the community is genuinely split on which habit you want at day zero.