Deschide articolul original într-un tab nou Schimbarea acestei opțiuni se aplică imediat și reîncarcă pagina.
LECTURA
Înapoi la articole →

Lionshead Notes

lionshead.digital/notes/rss.xml
Vizitează site-ul

Cel mai recent articol

Ultima verificare

Urmăritori 0 urmăritori
Articole: 12

  1. Invariant checks: the comment is the check you never wrote.

    (Lionshead Notes)

    I built a check that audits my own standards for gates that don't exist.

  2. My retro proposed three fixes and built none of them. Its health check read fine the whole time.

    (Lionshead Notes)

    The retrospective pass I said had never run had already run, twenty-nine minutes before the post saying so.

  3. The fleet that builds my backlog: two roles, one budget, and a rule against thinking

    (Lionshead Notes)

    How the agent fleet driving my product is actually wired.

  4. I handed my backlog to an agent fleet for ten days. Three of its safeguards were lying to me.

    (Lionshead Notes)

    I built a two-role agent fleet to drive my story queue: an expensive planner holding the whole graph, and a cheap executor forbidden from thinking.

  5. Killing the long-lived tokens in my CI, one exchange at a time

    (Lionshead Notes)

    A static service token in GitHub Secrets is a breach with the timer already running.

  6. How do you know a passing check still works? Make it fail on purpose.

    (Lionshead Notes)

    Last post I found four checks that had silently stopped working.

  7. I audited 2,864 CI checks. Several had never run, and green never told me.

    (Lionshead Notes)

    I counted every PR check I have ever run to answer a simple question.

  8. Every pull request gets its own app and its own Postgres branch, for $0

    (Lionshead Notes)

    Every Lionshead PR spins up its own running app and its own copy-on-write Postgres branch, created in seconds, deleted on merge.

  9. The security checks in every Lionshead PR

    (Lionshead Notes)

    At enterprise scale, a breach is a bad quarter.

  10. I'm one person, and my CI does what a mid-size eng org's does. Here's why.

    (Lionshead Notes)

    Lionshead PRs run a security suite, a cost gate, IaC scanning, and per-PR preview environments before any merge.

  11. Every website should have a colophon

    (Lionshead Notes)

    A small page that tells you how this site was built.

  12. Keeping 10 repos in sync without a monorepo or a platform team

    (Lionshead Notes)

    Distributing standards across ten small repos without a monorepo.