Skip to content
Writing5 pieces

Writing

Playbooks are standards I would bring to a team — currently, how to keep repository health, review capacity and architectural coherence intact when code generation gets cheap. Below them, an archive of earlier articles.

The design write-ups live with the systems they belong to, over in Work.

Playbooks
1
Articles
4
Decision records
In Work
01Playbooks

Standards & governance

Each one leads with the single rule it exists to enforce.

  • AI SDLC Governance10 Aug 2026

    AI-accelerated, architecture-gated: an SDLC that survives fast code

    Generation speed is only a gain if review capacity scales with it. Move the human bottleneck from writing code to specifying and verifying it.

    Teams adopting AI coding tools rarely fail because the generated code is bad. They fail because throughput outruns the review, testing, and architectural judgement that used to be applied at a slower rate. These are the gates I put in front of that.

    • SDLC
    • Code review
    • Testing
    • Governance
    Read the playbook
02Archive

Earlier articles

Shorter pieces written while I was learning in public. Kept as published rather than quietly deleted.

2023