Last write wins is a decision, not a default
When two writes reach one record and no code decides between them, the policy is whichever ran last. Name the resolver so the choice becomes reviewable.
Engineering
Compose, Kotlin, and multiplatform work — the mechanism under the symptom.
296 posts
A screen nothing navigates to still compiles
A route with no caller compiles, registers and never runs. Reachability is a graph property, so no per-file check can see it and nothing fails.
A hardcoded dp is a token you did not name
A literal spacing value is a token nobody named. The cost is not inconsistency now but that a redesign cannot distinguish values that happen to match.
The banking API that deliberately will not tell you things
Fineract exposes a restricted self-service namespace rather than the full API. What it omits is a design decision, and it shapes the whole client.
The only screenshots worth committing
Golden references are test inputs and belong in version control; run captures are regenerable evidence and do not. Conflating them loses the reference.
The module that compiled and was never installed
A dependency module nobody included compiles cleanly and fails at runtime. Declaration and installation are separate acts and only one of them is checked.
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.
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 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.
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.
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.