Stop hand-registering what a processor can see
A registry, a binding and a cleanup hook maintained by hand are three chances to forget. A processor already has what it needs to write all three.
All posts
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.
The numbers worth watching, and the ones that flatter
Vanity metrics are the easy half. The harder problem is a count whose derivation is wrong, because it reports confidently and nothing contradicts it.
The string literal that cannot be translated
A hardcoded string is not just untranslated — it is invisible to the sweep that finds untranslated text, so coverage reports complete while it is not.
One social card for every post is one card nobody shares
A single site-wide social card passes validation and makes every shared link identical. Per-post cards need generating, verifying, and a scan for the fallback.
Your list flickers because the page swap is not atomic
Replacing a cached page is several row operations, and a reader arriving between them observes a state that never existed. Make the swap one transaction.
Compose is doing what you told it; the instruction was wrong
Recomposition scope is set by where a value is read, not where it is declared. Most Compose performance problems are a read placed higher than it needed to be.
An app store is a discovery surface. A website is a building.
A store bundles search, ranking, category and the install action into one surface. On the open web each of those is a thing you build separately.
A testTag is a contract between the screen and its test
Tests that assert on visible text break on copy edits, which trains people to weaken assertions. A test tag is a deliberate contract that survives rewording.
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.