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.
All posts
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.
A hand-typed branch name skips the machinery
A branch name tidier than the generated one silently opts out of every automation that discovers work by parsing it. The naming was the interface all along.
Where a secret lives should never be a decision
Six consumers each deciding where a keystore lives agree until one changes. One registry keyed by stack and category, one resolver, no direct reads.
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.
A task that captures Project is a bug, not a gap
Calling it a configuration cache incompatibility frames a real defect as a missing feature. The task captures a live object where it should capture a value.