Skip to content

Field notes

Short, evidence-first write-ups of what I've actually observed building with LLMs — each one with the sample size stated and the ten-minute check to falsify it yourself.

AER v5: a compact contract for complete engineering

4 min read

AER v5 puts complete behavior, engineering judgment, and proportionate verification in a 45-line universal kernel, delivered locally for Claude Code and Codex.

  • agents
  • engineering judgment
  • verification
  • release engineering

A zero exit code is not evidence: what changed in AER 3.1

3 min read

AER 3.1 turns observed agent failures into explicit, cross-platform engineering checks without abandoning its compact progressive-disclosure model.

  • agents
  • developer tooling
  • validation
  • release engineering

The agent treated missing infrastructure as fate

1 min read

For a thousand lines it logged Docker's absence as a constraint and deferred the integration suites; told it could start the daemon itself, it did — and the suites it had been deferring found three real bugs.

  • agents
  • verification
  • infrastructure

Your rules file is not being read

2 min read

I measured a predecessor engineering-rules setup and found that only 13.2% of routed files were loaded. Rewriting the rules was never going to fix that.

  • agents
  • evaluation
  • context engineering

Five of eighteen runs invented evidence. One refused to.

1 min read

In a batch of runs designed to tempt fabrication, five invented a missing fixture to force a red gate green — and the catch that mattered came from an agent cross-checking primary sources, not from a rule.

  • agents
  • evaluation
  • fabrication

The only rule that worked is one a machine could check

2 min read

"Reproduce the failure before editing" produced 3/3 reproductions against 0/6 without it; the same idea phrased as a principle — "root cause before editing" — produced zero.

  • agents
  • rules
  • evaluation

The rules that help your best model can hurt your cheapest

2 min read

The same rules file was strongly net-positive for the stronger model and mixed-to-negative for the weaker one, where tests decreased and two regressions plausibly traced to the rule text itself.

  • agents
  • rules
  • model selection

Agents patch symptoms until you tell them not to

2 min read

Across three PRs, the agent handled review comments one at a time until I explicitly asked it to connect the failures and investigate the underlying mechanism.

  • agents
  • code review
  • root cause

A vague finish line produces laps, not progress

1 min read

With "continue remaining items" as the stop condition, the grader rejected the agent twice — not for bad work, but for declaring victory and then for asking me what to do — until it decided for itself.

  • agents
  • stop conditions
  • autonomy

Contact

Let's build something that ships.

Open to conversations about senior and staff frontend work, AI application engineering, and hard product problems. The fastest route is email.

© 2026 Abdallah Arslan · Atlanta, GA · Remote

React 19 · TypeScript · Tailwind · WebGL · d dark mode · ⌘K commands