Access control
Security
Boundaries before convenience
Who may do what? Define permissions, then test both allowed and denied operations.
Blog / Tim Witter
Writing
Safer systems, useful agents, verifiable software. Engineering perspectives with concrete code examples.
Explore the articles
14 of 14 articles
- Security scans
Quality & evidence
Coverage before clean reports
No findings or no inspection? Make coverage gaps in security reports visible.
- Tool design
Agents & tools
A small, discoverable tool surface
Make tools easy to discover without turning visibility into permission to use them.
- Architecture evidence
Architecture
Separate levels of architecture evidence
What do designs, tests, builds, and runtime checks actually prove? Match each claim to its evidence.
- Code navigation
Architecture
Structural navigation with honest unknowns
Use code indexes to find relevant source faster, without guessing at unresolved connections.
- Agent environments
Agents & tools
A predictable environment for agents
Pinned tools and durable instructions make agent-assisted work easier to reproduce and review.
- Sandboxing
Security
Proportionate isolation, not safety badges
Choose isolation for the actual risk. What a sandbox protects, and what remains outside it.
- Approval boundaries
Security
Permission to prepare is not permission to act
Planning is not execution. Use previews and explicit approval before changing shared state.
- Project checks
Quality & evidence
Verification is a project contract
Choose the right project checks and distinguish passed, failed, and not run in the handoff.
- Project setup
Architecture
Scaffolding without surprises
Generate a project scaffold without overwriting existing work: preview, change, then verify.
- Source review
Quality & evidence
Research needs an evidence trail
From search result to supported claim: read sources, retain evidence, and name uncertainty.
- Test design
Quality & evidence
Evaluate the claim you actually make
Challenge tests with near misses and ambiguous cases so a green result supports the actual claim.
- Contextual guidance
Agents & tools
Skills belong at the moment of need
Offer specialized guidance at the right decision point without replacing the project's rules.
- UI review
Quality & evidence
Visual quality comes from iteration, not a score
Inspect interfaces across sizes and states, fix a specific problem, then recheck the result.