The lock held across a network call, and the deadlock that followed
A mutex held for microseconds is fine. Held across an unbounded wait, it serialises your service.
All posts
The rollout with no off switch, discovered at 2am
A flag that gates the new path but not the data migration is not a kill switch.
Compose builds a second tree, and it's the one your users hear
Every Compose UI produces a semantics tree alongside the layout tree. It's what screen readers read, what tests query, and what autofill inspects — so getting it right serves three audiences at once.
The config change that was really a deploy, and had none of the safeguards
Config bypasses code review, CI, canaries and rollback. It changes behaviour just as much.
The N+1 query that looked fast in development
Ten rows locally, ten thousand in production. The query count scales with data.
Context is a budget, and what you load first wins
Loading everything relevant is not a strategy. Measure tokens per decision.
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.