Engineering

Tooling and technical governance

I like tools that help me understand a change before I rely on it. Local runs, prompt diffs, fixtures, and readable traces all make that easier.

Shortening the feedback loop

The closer a useful check is to the work, the more likely I am to use it. I build small tools when a larger project needs a repeatable way to verify something.

Keeping changes understandable

Schemas, interfaces, and prompts affect other parts of a system. Versioning and review help the next person understand what changed and why. Often that person is me, a few months later.

Open questions

  • Can a prompt or schema change be reviewed as a diff?
  • What can be run locally before it is trusted?
  • Which interfaces are contracts, and who is allowed to break them?