Skip to content

Will Banks

Technical writer and research engineer focused on developer documentation, complex systems, and docs-as-code workflows.

I create documentation that helps technical users adopt complex tools faster and helps engineering teams scale clarity alongside product complexity.

10+ years across technical writing and research engineering
Focus: SDKs, APIs, conceptual docs, docs-as-code, technical systems
Domains: defense-adjacent systems, avionics, biomedical platforms, AI-adjacent tooling

View Resume (PDF) →
LinkedIn →

Selected Case Studies

  • cnquery Practical Guide

    Scenario-driven CLI documentation for a security tool, written to improve task success for technical users.

    Focus: how-to docs, developer UX, task flow

    Read case study →

  • NodeZero Tripwires Redline

    A structural and editorial redline showing how I tighten flow, reduce ambiguity, and improve usability in existing product docs.

    Focus: redlining, information architecture, usability

    Read case study →

  • Chains vs. Agents in LangChain

    A conceptual explainer for developers choosing between fixed workflows and agentic architectures.

    Focus: conceptual docs, diagrams, onboarding clarity

    Read case study →

Articles & Essays

I also write analytical pieces on where technical writing is heading as it becomes more tightly integrated with AI systems, docs-as-code workflows, and modern software delivery.

  • OASBuilder and Automation-Ready API Docs

    Why API documentation is becoming directly relevant to machine-readable interfaces and downstream automation.

    Theme: API docs, automation, documentation as infrastructure

    Read article →

  • DocAgent and Multi-Agent Documentation Pipelines

    What multi-agent generation and verification workflows suggest about the future of documentation CI.

    Theme: AI-assisted docs, verification, agentic workflows

    Read article →

  • Outdated Documentation as a Repository Integrity Problem

    Why certain documentation defects should be treated like CI-detectable repository failures instead of editorial drift.

    Theme: docs-as-code, CI, referential correctness

    Read article →

Browse all Articles & Essays →

Governance & AI Workflows

I also maintain a standalone HTML micro-series on governing long-lived AI-assisted work: identity preservation, bounded revision, authorization, and convergence across multiple cycles of collaboration.

  • Governing LLM-Assisted Work

    A three-piece framework series plus companion architecture note on how to structure long-lived AI-assisted projects so they do not quietly drift, self-authorize, or converge on the wrong object.

    Best entry point: The Frozen Anchor

    Open the series →

How to Read This Portfolio

Each sample is meant to show a different mode of documentation work:

  • How-to guidance for technical users trying to complete a task
  • Redline/editing work that improves clarity, structure, and usability
  • Conceptual explanation that helps developers build accurate mental models
  • Articles and essays that examine documentation as part of the development lifecycle
  • Framework essays that examine governance and long-lived AI-assisted workflows

For a fuller view of the workflow behind this site, see Workflow & About.

Contact

Reach me at william.e.banks@icloud.com or on LinkedIn.