1. The Case for Publishing a Useful Package Early

    PyPI names are scarce, pending publishers do not reserve them, and active conflicts are hard to unwind. A small working release can be the responsible first public commitment.

  2. A Release Has Three Trust Decisions

    Version identity, permission to publish, and artifact integrity answer different questions. A release pipeline is trustworthy only when it connects all three.

  3. Testing the Package Beyond the Source Tree

    Several upstream fixes point to one packaging rule: exercise built artifacts, disabled paths, and dependency boundaries directly.

  4. One Review Inbox for Two Forges

    tongs treats code review as one terminal workflow across GitHub and GitLab, then designs each layer around the differences that remain.

← All writing