ABAllen Brooksinlionshead-notes.hashnode.dev·Aug 10 · 14 min readI handed my backlog to an agent fleet for ten days. Three of its safeguards were lying to me.I have a launch with a date that does not move. I also have a job between eight and five, a two year old, and a four month old. Everything I build, I build around those. So the binding constraint is n00
ABAllen Brooksinlionshead-notes.hashnode.dev·Aug 3 · 9 min readKilling the long-lived tokens in my CI, one exchange at a timeA static API token stored in GitHub Secrets is a breach that has not happened yet. The timer is already running. You do not know how long the fuse is, because a long-lived token's fuse is however long00
ABAllen Brooksinlionshead-notes.hashnode.dev·Jul 31 · 6 min readHow do you know a passing check still works? Make it fail on purpose.A feature makes money. A check protects it. Those are not the same job, and the difference is why checks rot. When you ship a feature, the market tells you fast whether it works. Someone signs up or t00
ABAllen Brooksinlionshead-notes.hashnode.dev·Jul 31 · 9 min readEvery pull request gets its own app and its own Postgres branch, for $0Every place I've worked plumbed everything to one shared dev environment. One database, one deploy, everyone's half-finished work landing in the same place. The database slowly filled with test accoun00
ABAllen Brooksinlionshead-notes.hashnode.dev·Jul 31 · 9 min readThe security checks in every Lionshead PRAt enterprise scale, a breach is a bad quarter. You have a legal team to coordinate disclosure. A disaster-recovery plan you drill annually. A PR team to control the narrative. A security team to quar00