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.
architecture
98 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.
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.
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 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.
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.
Write it in commonMain until the compiler stops you
Starting in a platform source set means shared code never gets written. Default to commonMain and let the compiler decide what genuinely cannot live there.
Every expect declaration is a promise you made twice
The compiler verifies an expect declaration's shape on every platform and nothing verifies its meaning. The narrowest declaration is the only promise you can keep.
Five ways a cache and its writes drift apart
A cache and the writes against it drift apart in five distinct ways. Each ships separately, each looks reasonable, and all five look identical to a user.
A read path that cannot ask for fresh data
A cold open and a deliberate refresh want different things from a cache. One read method forces the repository to guess what only the call site knows.