Context is a budget, and what you load first wins
Loading everything relevant is not a strategy. Measure tokens per decision.
Engineering
Compose, Kotlin, and multiplatform work — the mechanism under the symptom.
229 posts
Take the clock away and animations become testable
Compose tests idle-wait by default, which makes animated UI either flaky or untested. Disabling autoAdvance gives you frame-level control, turning 'wait and hope' into deterministic assertions at chosen moments.
The retrieval worked and returned the wrong file
Semantic similarity is not relevance. A test file and its subject are near-identical in embedding space.
A shared element transition is one element pretending to be two
Shared element transitions match two composables by key and animate between their bounds. Understanding that neither element travels — a third overlay draws the motion — explains the scope requirements and the common failures.
The agent fixed the test, not the bug, and the test was right
Given a failing assertion, weakening it is the shortest path to green.
The eval that passed because the function returned a plausible stub
An LLM judge scoring output shape rather than behaviour will approve a stub.
An agent loop without a terminal condition is a budget with no bottom
Declare the halt classes before the loop runs. 'Until it looks done' is not a condition.
You cannot fade out something that has already left the composition
An element removed by an if is gone immediately, so an exit animation has nothing to animate. AnimatedVisibility keeps it composed until the exit finishes — and AnimatedContent does the same for swaps.
Your agent's tool output is untrusted input
A file the agent reads can contain instructions. The fix has the same shape as SQL injection's.
The cache that returned someone else's data
A cache key missing the tenant is a data leak with a 100% hit rate.
Every timeout you set independently adds up to one that is wrong
Three services with 30-second timeouts give the user 90 seconds.
updateTransition is a state machine that happens to animate
updateTransition coordinates several animations driven by one state. It handles multi-state enums, per-property specs via transitionSpec, and child transitions — all with coherent interruption a group of animate*AsState calls cannot give you.