Partial translation is a number, not a feeling
Per-locale coverage against the base key set is a number you can compute every release — without it, shipping a language is a guess nobody owns.
tooling
36 posts
Three repositories, one change, and the order that stops it corrupting
Submodule pointers make commit order load-bearing. Parent first records a SHA nobody else can fetch, and automation can silently revert one.
Every .env file in my projects is gone and nothing broke
A local secrets file is a copy nobody controls. An encrypted vault that materializes per ecosystem removes the copy rather than protecting it.
What act can reproduce, and what it silently cannot
Local workflow runners reproduce containerised jobs faithfully and host jobs not at all. Skip-and-warn is the only honest handling of the gap.
Your deploy said zero changed because it never looked
A deploy that ships whatever is already built never regenerates. Fifteen posts had new frontmatter, it reported 0 changed, and every link stayed stale.
Killing the Gradle daemon costs you thirty minutes
Killing a build daemon discards the configuration cache, build cache, file watching and JIT state at once. Forty seconds becomes half an hour.
Forty-five minutes per CI guess is not a feedback loop
Reproducing a failing CI job locally turns a 45-minute guess into a 2-minute iteration. What runs locally, what cannot, and why faking the rest is worse.
A documented workflow nothing could execute
A guard blocked the one step a documented runbook required. The fix was not a weaker guard, it was building the sanctioned command it was asking for.
An auth gate you do not resent
A gate asked too often gets automated away, and one asked once never expires. Charge full authentication only for transitions that change the threat model.
Two modules with the same name, one is a demo shell
A generator wrote a feature into a template demo module sharing the real one's name. Resolve the target from disk and halt on ambiguity rather than picking.
429 is not an error, it is a schedule
Transient and terminal failures need opposite responses and look identical. How to tell them apart, and why partial progress must be persisted before it is believed.
Write down what you did to an external service
A create-only API cannot answer whether a thing exists. The local ledger becomes the sole source of truth, and one write's ordering decides if it works.