ABAllen Brooksinlionshead-notes.hashnode.dev·1d ago · 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·1d ago · 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·1d ago · 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
ABAllen Brooksinlionshead-notes.hashnode.dev·1d ago · 4 min readI'm one person, and my CI does what a mid-size eng org's does. Here's why.Corporate CI is often the red-headed stepchild of the dev team. Written six years ago by a consulting firm, held together with cron jobs whose owners left in two reorgs, touched only when it breaks. N00
ABAllen Brooksinlionshead-notes.hashnode.dev·1d ago · 2 min read Every website should have a colophonEvery developer I know has the same itch. Pop the hood on a website, a SaaS app, an app on the App Store, and see how it was built. Which framework. Which hosting. Which type. The craft underneath the00