The export engine that exported nothing
A stub is not an empty function. It returns plausible values, satisfies its interface and does no work, which is why emptiness checks never find it.
Engineering
Compose, Kotlin, and multiplatform work — the mechanism under the symptom.
229 posts
A retry queue with nothing to run it is a graveyard
A failed-sync flag is not a retry mechanism. Three parts are needed: a connectivity signal, an enumeration of what failed, and backoff with a ceiling.
The corpus your generator reads is production code
The corpus a generator reads is as load-bearing as the code it emits. A hand-edit to it has no provenance and is dropped by the next re-sync.
Five buttons, one hierarchy, and the rule that decides which
Material 3 ships five button styles plus the FAB. They form an emphasis hierarchy, and the selection rule is about how many actions compete on a screen rather than about how each one looks.
It compiles, the test is green, and the screen is a grey box
A structural shell passes an AST scan and a unit test while rendering nothing the mockup specified. Only a rendered check can tell the difference.
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.
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.