Tagged #tooling
6 notes.
CI can deploy to Cloud Run without a key — and one missing line trusts all of GitHub
How Workload Identity Federation replaces a service-account key in GitHub Actions, which three IAM grants a deploy actually needs, and the two flags that quietly decide whether your service survives the deploy.
The follow-up: Biome shipped, Mago didn't — what the Catroweb migration actually taught me
Three weeks ago I promised real numbers instead of vendor benchmarks. Here they are: Biome replaced ESLint+Prettier and stuck, Mago got screened out before it ever ran, and the thing that ate my afternoon was a supply-chain scanner nobody asked about.
One extension codebase for Chrome and Firefox — signing is the only real fork
The same unpacked MV3 folder loads in both browsers; the divergence is how you get a permanent install, and Firefox's signing story is friendlier than its reputation.
Coding from my phone works because none of it runs on my phone
Claude Code on the web runs each session in a cloud VM, so closing the browser doesn't stop the work — I shipped two small apps from a train with no laptop.
I told Claude Code to build its own status line
The status line is just a script that gets handed a JSON blob — git branch, files changed, usage limits — so building one is mostly describing what you want.
Trading four linters for two: Biome and Mago vs my Prettier/ESLint/PHPStan/Fixer stack
A theoretical, table-by-table comparison of the Rust linting toolchains Biome and Mago against the Node/PHP incumbents — before I migrate a real project and report the actual numbers.