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.
architecture
70 posts
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.
On-device semantic search over the user's own data
Semantic search on a phone is not a vector-database problem at user scale — it is an index-freshness problem, invisible until someone searches.
Gemini Nano on-device: what it actually costs you
On-device inference has no per-call bill, and that hides six real costs — eligibility, size, battery, thermal, capability ceiling and operations.
Routing between a local model and a remote one
Routing between a local and a hosted model needs a decision you can audit. Route before attempting, record the path on every result, and watch the proportion.
An AI feature that still works on a plane
Reading offline is the easy half. The write path is where it breaks: stale cold starts, unresolved conflicts, unorchestrated retries and torn pages.